WordPress Update, Hacked Websites, Vulnerabilities, Glossary & Support Forum Discussion
This post was curated and edited by Ben Gillbanks. Ben is a WordPress user and developer with over 20 years experience of building things online.
Hello and welcome to WP Briefs, your Artificial Intelligence source for the latest news and updates in the WordPress world. Today is Thursday 17th August 2023.
In today’s news, we have several stories related to WordPress and its community. Let’s dive in and explore each one.
First up, WooCommerce Blocks has released its latest version 10.9.0 1. This update brings an exciting integration with the Interactivity API, particularly enhancing the shopping experience by integrating the Product Button. However, it is worth noting that there is a known issue where the Product Button doesn’t work when the Products (Beta) block is loaded with the Classic Placeholder block.
Moving on, a recent report highlights how nearly 150,000 WordPress websites were hacked within a 60-day period 2. Surprisingly, popular security plugins were unable to detect malware that added itself to their allow lists. This discovery raises questions about the effectiveness of these security plugins and calls for further investigation into improving website protection.
On the topic of vulnerabilities, a new WordPress Vulnerability Report reveals that 90 total vulnerabilities have emerged since last week 3. These vulnerabilities have the potential to affect over one million WordPress sites. It is crucial for website owners to promptly update their plugins and themes to ensure they are not exposed to any security risks.
If you’re planning on attending WordCamp Europe (#WCEU) or WordCamp US, it’s essential to familiarize yourself with some WordPress-specific terms 4. The WordCamp Glossary provides over 30 terms that will help you navigate and engage in conversations during this event.
Lastly, there is a discussion taking place regarding auto-closure of support forum threads on WordPress.org 5. Currently, threads automatically close after a year unless manually closed sooner than that. A proposal suggests removing auto-closure and instead adding a warning when a thread becomes old. This change aims to ensure users can continue receiving support even if their thread has been inactive for some time.
That wraps up today’s news on WordPress and its community. Stay tuned for more updates in the future.
If you enjoyed this episode, please tell your friends. For the transcript and links to the articles mentioned in this episode, please visit wpbriefs.com. Thanks for listening and we’ll see you soon.
