· via dev.to (home feed)
WordPress.org now blocks high-risk plugin releases with automated security reviews
WordPress.org's Plugins Team now screens every plugin release with an automated security review before it ships through the update API, and high-risk versions are blocked. Coverage is limited to directory-distributed plugins.

What changed
Every plugin release on WordPress.org is now subject to an automated security review before it is distributed through the directory's update API. According to a dev.to report on the change, the WordPress.org Plugins Team announced the policy on September 9, 2026, and releases that the system scores as high risk are automatically prevented from reaching sites that pull updates from WordPress.org.
The practical effect is that a platform-level gate now sits between a developer publishing a release and that release arriving on live sites. Update delivery is no longer purely a matter between the plugin author and each site's administrator.
How the screening works
The dev.to article describes the review process as combining multiple AI models with Jetpack Scan, evaluating each release before the update API distributes it. Related Plugin Handbook guidance documents the policy and where it fits into the release workflow.
Automated pre-distribution checks are not a guarantee that every unsafe release gets caught. What they do add is a checkpoint before directory-hosted code is delivered at scale.
Why the gate exists
Plugin updates are a well-known supply-chain risk: when a popular plugin pushes a compromised release, its installed base can accept it automatically, hitting thousands of sites almost at once. The source points to the Advanced Responsive Video Embedder (ARVE) incident as an illustration, in which a backdoor was found in a release affecting roughly 20,000 active installations.
The broader context includes WordPress core itself. Per the dev.to report, the WordPress 7.1.4 security release documented a critical time-of-check to time-of-use (TOCTOU) vulnerability in the upgrade process. That core fix is separate from the plugin release policy, but it reflects the same ecosystem-wide effort to tighten update security.
A cooldown already changed update timing
The review follows another recent change to update delivery. On June 5, 2026, WordPress.org introduced a cooldown window before plugin updates flow through to live sites, and reporting cited by dev.to indicates the window was later reduced from 24 hours to up to six hours.
The two measures address different risks. The cooldown creates time between a release and broad delivery, while the automated review evaluates security risk before distribution. Neither replaces a site's own testing, backups, monitoring, or access controls.
What is and isn't covered
The review's scope is narrower than "all WordPress plugins." It applies to releases distributed through the WordPress.org directory and its update API. The dev.to report breaks the remaining cases into three groups:
- Directory plugin updates: covered by the announced review workflow.
- Premium or commercial plugin updates: not necessarily covered, so teams should assess the vendor's release, security, and rollback practices separately.
- Custom or manually installed ZIP plugins: not covered, leaving internal code review and controlled deployment as the only safeguards.
For agencies and larger publishers, that distinction matters. A site may rely mostly on directory plugins while running one custom integration or paid extension for a business-critical function, and the WordPress.org review reduces risk for only part of that stack.
What site owners should still do
The change lowers the risk baseline for one update channel but leaves site-specific compatibility risk intact. A perfectly legitimate update can still conflict with a theme, caching configuration, ecommerce extension, or custom code. The dev.to report recommends that teams:
- Keep an inventory of which plugins update through WordPress.org and which do not.
- Test material changes in staging when the site has custom functionality or revenue-critical pages.
- Monitor uptime and server errors during and after update windows.
- Check crawl errors, index coverage signals, and template rendering after deployments.
- Watch Core Web Vitals and other performance indicators for unexpected regressions.
- Keep tested backups and a documented rollback path.
Why it matters
Plugins are the main way WordPress sites gain functionality, and historically also a main way they get compromised. Inserting an automated security gate between developers and the many sites that auto-accept updates is a meaningful governance change for the plugin supply chain, and it can stop a dangerous release before it scales the way the ARVE backdoor nearly did.
Two caveats keep expectations realistic. First, coverage stops at the WordPress.org update channel: premium, custom, and manually installed plugins receive no protection. Second, as the dev.to report is careful to note, there is no published evidence tying the review to search rankings; any SEO benefit is indirect, through fewer incidents that cause downtime, broken rendering, or compromised pages. Site owners should treat this as useful risk reduction on one channel, not as a substitute for staging tests, backups, and monitoring.
- #wordpress
- #plugins
- #security
- #software-supply-chain
- #updates