Matt Mullenweg announced on June 5 that WordPress.org will now hold every new plugin release for up to 24 hours before it reaches sites through auto-updates. The change flips what was previously an opt-in feature into a platform-wide default, covering all 61,000-plus plugins in the official directory. Site administrators can still apply updates immediately through their dashboards. The delay only affects the auto-update pipeline.
The infrastructure behind this was already running. Mullenweg introduced phased plugin releases as an opt-in option back in August 2025, and plugin authors who wanted to delay distribution could enable it on individual releases. The June announcement removes the choice and makes the hold universal. The stated reason is straightforward: AI tools have made it easier to slip malicious code into a legitimate plugin release and distribute it to millions of sites before anyone notices.
Two incidents shaped the decision. The Essential Plugins backdoor sat dormant inside 31 plugins for eight months before activating in April 2026 against more than 20,000 sites. Around the same week, a compromised update for Smart Slider 3 Pro spent roughly six hours in the update channel before anyone caught it. Both cases followed the same pattern: malicious code in a release, distributed at scale, before the directory could respond.
The 24-hour buffer gives an AI-assisted review system, referenced in the post under the name Gandalf, time to scan each release before it goes out. Mullenweg signaled the window could shrink as the tooling matures, but for now caution wins.
The tradeoff is real and worth naming directly. Patchstack’s 2026 security research found that roughly half of high-impact WordPress vulnerabilities are exploited within 24 hours of disclosure. That means the same delay protecting sites from a malicious release also slows down legitimate security patches reaching the auto-update pipeline. Hosts running their own vulnerability monitoring can still push verified patches manually and immediately. Hosts that rely entirely on WordPress.org’s distribution cadence will feel the delay directly.
For managed WordPress hosts specifically, the decision shifts what was previously a host-level policy choice into a platform-level default. Some hosts already introduce their own review delays. Others will need to rethink how they communicate update timelines to customers.
The change went live through a blog post, without a formal community process or open proposal.

