Plugin Vulnerabilities

Plugin Vulnerabilities

@pluginvulns.bsky.social

Provider of service to protect websites from being exploited due to vulnerable WordPress plugins. https://www.pluginvulnerabilities.com/

66 followers26 following1.1K posts

With Automattic announcing a return to contributing to WordPress, it's worth noting that there hasn't been a change with the cited reasons they gave for reducing their contributions in January. WP Engine's lawsuit is still on and they haven't boosted their contributions.

automattic.comAligning Automattic’s Sponsored Contributions to WordPressAutomattic has always been deeply committed to the success of WordPress, dedicating significant resources and talent to its development for almost two decades. However, we’ve observed an imbalance …

A WordPress plugin with 100,000 installs has an unfixed vulnerability being targeted by a hacker and Patchstack's response is to suggest you pay them $5 a month for a firewall rule they call a "patch". WordPress could release a real patch for free. We would provide them with the patch for free.

patchstack.comUnpatched Critical Vulnerability in TI WooCommerce Wishlist Plugin - Patchstack🚨 A critical unpatched vulnerability in the TI WooCommerce Wishlist plugin allows unauthenticated file uploads and potential RCE. Over 100K sites affected. As usual, Patchstack users are protected. 🛡️

Mary Hubbard: "Rotating roles can help us avoid centralizing too much authority in any one place, and it guards against the single points of failure that open source and communities should always aim to minimize." Is rotating roles going to apply to her boss Matt Mullenweg?

Mary Hubbard goes on to say "If we continue to center empathy, transparency, and the shared goal of making WordPress better for everyone, we won’t just be stronger. We’ll be ready for whatever comes next." When has WordPress centered transparency?

8 months after a vulnerability was reported to someone, it still hasn't been fixed. It's unclear what happened here, but the developer claims that the vulnerability was reported to @patchstack.com instead of to them. They say Patchstack made a public claim after 6 months, but didn't notify them.

Plugin Vulnerabilities@pluginvulns.bsky.social

Is Brizy, Patchstack, or Both to Blame For Lack of Fix for Vulnerable WordPress Plugin With 80,000+ Installs After 8 Months?

They don't mention how many website are using the new plugins. A quick check of our lagging data shows that almost all of the plugins added to the directory this year have under 100 installs. With only slightly over 2% above that. And roughly 83% having under 10 installs.

The FAQ for the Brizy WordPress plugin tells you to report issues through GitHub and links to a page to do that. If you try to create an issue, it doesn't work with the vague message "Unable to create issue." returned. 1/2

github.comPull requests · ThemeFuse/BrizyBrizy is the most user-friendly visual page builder in town! No designer or developer skills required. The only tools you'll need to master are clicks and drags. - Pull requests · ThemeFuse/Brizy

Looking at the underlying response sent from GitHub, it actually contains a clear explanation, "Issues has been disabled in this repository." Why is @github.com making the issue reporting form available in that situation and why isn't it showing the clear explanation when submission fails? 2/2

Instead their response is to suggest spending more money on web hosting: "Hosting that handles plugin updates and scans for vulnerabilities lets users enjoy the power of WordPress without the pressure." (Their vulnerability scanning clearly doesn't work, as can be see by their own plugins.) 4/

They had this to say about WordPress plugins: "Plugin fatigue – the frustration users feel from maintaining too many plugins – often results from constant updates, compatibility issues, performance slowdowns, unexpected security vulnerabilities, and rising costs." 2/

Someone is trying to exploit a claimed vulnerability in the WordPress plugin WHMpress. We are not using the plugin, but it didn't stop them from trying multiples times despite being blocked each time by our Plugin Vulnerabilities Firewall.

It's 2025 and the Yoast SEO WordPress plugin still doesn't properly uninstall. It leaves behind multiple options and database tables, despite it clearly being stated those should be removed. And @joost.blog thinks he should be in charge of WordPress.

developer.wordpress.orgUninstall Methods – Plugin Handbook | Developer.WordPress.orgYour plugin may need to do some clean-up when it is uninstalled from a site. A plugin is considered uninstalled if a user has deactivated…