The WordPress.org vs. WP Engine Fallout: What It Means for Plugin Users

WordPress powers a huge share of the web, which is exactly why the very public fight between WordPress.org and WP Engine mattered beyond the two companies involved. If you run a WordPress site — regardless of who hosts it — the fallout from this touched the plugin ecosystem in ways that are worth actually understanding rather than half-remembering from headlines.

How it actually started

At his WordCamp US keynote on September 20, 2024, Matt Mullenweg — co-founder of WordPress and CEO of Automattic — called WP Engine “a cancer to WordPress,” contrasting Automattic’s reported roughly 3,915 weekly contributor hours to WordPress core against WP Engine’s roughly 40. The next day, WordPress.org published an official post titled “WP Engine is not WordPress,” arguing WP Engine needed a trademark license and criticizing the company for disabling post revisions by default across what Mullenweg described as 1.5 million installs, reportedly to reduce storage costs.

On September 25, 2024, WordPress.org blocked WP Engine’s access to the login.wordpress.org infrastructure that plugin and theme updates depend on — a move with real, immediate technical consequences for WP Engine customers’ sites. WP Engine sued Automattic and Mullenweg on October 2, 2024, in a 62-page federal complaint alleging tortious interference and extortion, centered on an alleged demand for an 8% revenue license.

The Advanced Custom Fields fork

On October 12, 2024, WordPress.org took the unusual step of unilaterally taking over the plugin listing for Advanced Custom Fields — a hugely popular plugin owned by WP Engine — and renamed it “Secure Custom Fields,” citing a specific plugin-guideline provision. This is the single most consequential technical event in the whole conflict for ordinary site owners: it meant WordPress.org itself, not just WP Engine, took direct control of updates for a plugin millions of sites depend on, without the original developer’s consent. That’s a level of intervention in the plugin repository that hadn’t really had a clear precedent before.

Whatever you think of either side’s underlying business dispute, the ACF takeover is the moment this stopped being a fight between two companies and became a demonstrated capability: WordPress.org can, in a dispute, take direct control of a plugin’s official listing away from its original developer.

Where the legal fight actually stands

A December 2024 court ruling granted WP Engine a preliminary injunction restoring its access to WordPress.org infrastructure. More significantly, on September 12, 2025, a judge dismissed the federal antitrust and monopolization claims, along with the California extortion claim — but allowed the tortious interference, unfair competition, and defamation claims to proceed against both Automattic and Mullenweg personally. Some reporting indicates the case is heading toward a jury trial as far out as February 2027, though I’d treat that specific date as secondary reporting rather than a confirmed court date.

So as of the most recent reporting available: this isn’t over, isn’t a clean win for either side, and several serious claims are still actively working through the court system.

What this actually means if you’re not WP Engine’s customer or Automattic’s rival

The practical takeaways for the average WordPress site owner or plugin user are narrower than the drama suggests, but genuinely real:

• WordPress.org demonstrated it can and will intervene directly in a plugin’s listing during a dispute. That’s a new-ish precedent worth being aware of, even if it’s unlikely to affect most individual plugins most of the time.
• If you were on WP Engine hosting during the access block, you may have directly experienced update delays — worth checking your plugin/theme update history from around late September 2024 if anything seemed off during that window.
• The ACF/Secure Custom Fields split is worth checking on your own sites. If you’re running Advanced Custom Fields, verify which version and source you’re actually running updates from, since the plugin effectively forked into two parallel listings during this dispute.
• The underlying trademark question — what “WordPress” as a name and mark actually covers, and who gets to license it — remains genuinely unresolved as an industry matter, separate from this specific lawsuit’s eventual outcome.

How this compares to past WordPress governance disputes

WordPress has weathered disagreements over trademark and governance before, but usually as slower-moving, lower-visibility disputes resolved through private negotiation rather than a public keynote accusation followed within weeks by infrastructure access being cut off. What made this one different in kind, not just in scale, was the speed and directness of the escalation — from a public “cancer” remark to a login-infrastructure block to a plugin-listing takeover, all within about three weeks. That compressed timeline is part of why it drew as much attention across the wider WordPress ecosystem as it did, well beyond the hosting-industry audience that would normally follow a dispute between one host and Automattic.

The bigger picture worth sitting with

WordPress has always relied on a somewhat unusual structure — an open-source project (WordPress.org) governed with real influence from a for-profit company (Automattic) and its founder, alongside a large ecosystem of independent commercial hosts and plugin developers who depend on that open infrastructure but don’t control it. This conflict is the clearest public demonstration in WordPress’s history of what happens when that structure comes under real strain. Regardless of how the remaining legal claims resolve, the precedent set by the ACF takeover — that WordPress.org’s governance can act unilaterally on a commercial plugin during a dispute — is the part of this story most worth remembering, independent of who eventually wins in court.