Plugin Vulnerabilities Customers Helped Make WordPress Plugins More Secure, Week of June 6
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
WordPress Firewall Plugin Claimed to Protect Against "Any Threat" Doesn't Stop Even One Simulated Attack From Firewall Testing Tool
Patchstack Now Withholding Misappropriated Information Needed to Secure Plugins in WordPress Plugin Directory From WordPress
Plugin Vulnerabilities Customers Helped Make WordPress Plugins More Secure, Week of May 30
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.
Also worth re-upping is that Five for the Future pledges are in general highly suspect. It is one of the many things that are need of reform with WordPress.
WP Engine Study Finds That Security Is Somehow Considered One of WordPress' Benefits and Also Disadvantages
Patchstack tries to get people to report plugin vulnerabilities to them instead of developers or WordPress. Now they are refusing to provide the information to WordPress.
Patchstack are claiming the EU Cyber Resilience Act (CRA) requires this. It isn't the first time they have lied about that act.
Patchstack tries to get people to report plugin vulnerabilities to them instead of developers or WordPress. Now they are refusing to provide the information to WordPress.
Joost de Valk (@joost.blog) is funding what is basically a man-in-the-middle (MiTM) attack against WordPress.
We provided our customers with the details of the vulnerability last week.
"we always take security seriously" - WordPress plugin developer who still hasn't fixed an exploitable vulnerability two months after apparently being notified of it
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 claimed today that over 100,000 websites are affected, but as we noted last week, it is significantly less than that.
WordPress Plugin Submission Review Seems to Have Failed Badly With ConvertPro
Plugin Vulnerabilities Customers Helped Make WordPress Plugins More Secure, Week of May 23
Long Overdue Security Review of WordPress Would Cost Only 0.25% of WP Engine's Estimate of Cost of One WordPress Website
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?
Restoring Trust while Preserving Safety
WordPress Hasn't Addressed Hacker Targeted Plugin With 100,000+ Installs That Has Unfixed "Critical" Vulnerability
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.
Is Brizy, Patchstack, or Both to Blame For Lack of Fix for Vulnerable WordPress Plugin With 80,000+ Installs After 8 Months?
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 WordPress Ecosystem is Growing: New Plugin Submissions Have Doubled in 2025
We have added the FV Gravatar Cache to the roster of WordPress plugins that receive continuous security review from us. That entails us reviewing every update to the plugins for any changes that impact security. If you want a plugin to get the same level coverage, we have a service for that.
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
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
Wordfence Missed That Authenticated Persistent XSS Vulnerability in 2+ Million Install MC4WP: Mailchimp for WordPress Wasn't Fixed
Patchstack VDP Partner WPMU DEV Incompletely Fixed Privilege Escalation Vulnerability in Broken Link Checker
Plugin Security Scorecard April Results
600k WordPress Backup Plugin Claiming to Be "Easiest Way to Protect Your Website" Contains Decade Out of Date Insecure Library
A developer thinks that if you find a vulnerability in their software you shouldn't be able discuss it without their "express consent": "Please do not discuss any vulnerabilities (even resolved ones) without express consent." github.com/timber/timbe...
Hacker Already Targeting Plugin With Vulnerability Exposed by Wordfence Today Without Fix Being Available
Liquid Web could do something about this, as among other issues, StellarWP keeps releasing incomplete security fixes for one of their plugins. Hiring someone to security reviews could get those issue fixed once, but they don't do that. 3/
Authenticated Information Disclosure Vulnerability in PrettyLinks
WordPress and Security Providers Fail to Make Sure All Plugins Containing Known Vulnerability Have Been Addressed
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.
The response to people pointing this out is to tell them to manually search through the database to try clean out the plugin. Seriously?
Is Hacker Using "Hallucinating" AI Chatbot to Create Exploit Attempts Against Non-Existent Vulnerabilities in WordPress Plugins?