Introduction
If you follow WordPress news even casually, you’ve probably seen the headlines. Lawsuits. Legal threats. Public accusations flying between two of the biggest names in the WordPress world.
And if you’re a business owner, developer, or agency running sites on WordPress, you’re probably wondering: should I be worried about this?
Here’s the honest truth. The WordPress lawsuit situation is real, messy, and genuinely important for anyone who uses the platform. It’s not just tech industry drama. It touches trademark rights, open-source ethics, commercial fairness, and the long-term future of the WordPress ecosystem.
This post breaks the whole thing down from the beginning. Who sued who. Why it started. What each side is claiming. What the courts have said so far. And most importantly, what this actually means for your WordPress website and your business.
No legal jargon. No corporate spin. Just a clear, honest account of one of the most significant legal battles WordPress has ever seen.
1. The Two Main Players: Automattic and WP Engine
Before we get into the lawsuit itself, you need to know who’s actually involved. Because this isn’t a lawsuit against “WordPress” as software. It’s a legal battle between two specific organizations with a complicated history.
Automattic is the company founded by Matt Mullenweg, one of the two original co-creators of WordPress. Automattic owns and operates WordPress.com, the hosted version of WordPress. Automattic also employs a significant number of the contributors who work on WordPress.org, the open-source project.
Matt Mullenweg is both the CEO of Automattic and the self-described “benevolent dictator” of the WordPress open-source project. He holds an enormous amount of influence over the direction of WordPress as a platform.
WP Engine is one of the largest managed WordPress hosting companies in the world. It hosts hundreds of thousands of WordPress websites for businesses and developers. WP Engine is a for-profit company backed by private equity. It generates significant revenue from the WordPress ecosystem.
Neither company owns WordPress as software. WordPress is open-source. But both have deep, financial stakes in the ecosystem WordPress created. That tension is the root of everything that followed.
2. What Actually Started the WordPress Lawsuit Drama?
The public conflict between Matt Mullenweg and WP Engine exploded into view in September 2024 at WordCamp US, one of the biggest annual WordPress community events.
Mullenweg gave a keynote address that directly and publicly attacked WP Engine. He accused WP Engine of taking enormous financial value from the WordPress open-source project while contributing very little back to it.
He called WP Engine a “cancer” to WordPress. He claimed the company contributed a disproportionately low share of development resources relative to the revenue it earns from the WordPress ecosystem. He pushed the argument that WP Engine was free-riding on a community it barely supported.
The speech was startling. Public figures in the WordPress community don’t usually call out specific companies by name in keynotes. It created immediate shockwaves.
WP Engine pushed back hard. They disputed Mullenweg’s characterizations of their contributions. They argued that managed hosting companies don’t have the same obligation to contribute code as software companies do. And they accused Mullenweg of using his platform position to damage a competitor to Automattic’s own WP Engine-adjacent hosting products.
That last point matters. Automattic runs WordPress.com, which competes directly with WP Engine’s managed hosting business. Critics noted that Mullenweg attacking WP Engine from a position of power over the WordPress.org infrastructure created a significant conflict of interest.
What started as a public dispute quickly escalated into legal action from both sides.
3. WP Engine’s Lawsuit Against Automattic and Mullenweg
WP Engine fired the first legal shot. In October 2024, WP Engine filed a lawsuit in the United States District Court for the Northern District of California against both Automattic and Matt Mullenweg personally.
WP Engine’s core legal claims included:
- Extortion and attempted extortion — WP Engine alleged that Mullenweg had pressured them to pay Automattic a significant licensing fee or face consequences. They claimed he threatened to use his control over WordPress.org infrastructure to damage WP Engine’s business if they didn’t comply.
- Trademark abuse — WP Engine argued that Automattic and Mullenweg used control over the WordPress and WooCommerce trademarks improperly to pressure WP Engine and restrict their business operations.
- Tortious interference — WP Engine claimed that Automattic intentionally interfered with WP Engine’s business relationships and contracts through its actions.
- Computer fraud — related to Automattic’s decision to block WP Engine’s access to WordPress.org resources.
The lawsuit painted a picture of Mullenweg using his outsized control over the open-source WordPress infrastructure as a weapon to serve Automattic’s commercial interests. WP Engine described this as an abuse of power that harmed both their business and the broader WordPress community.
This was a serious legal filing. Not a cease-and-desist letter. A full federal lawsuit with multiple causes of action seeking damages.
4. Automattic’s Counter-Lawsuit Against WP Engine
Automattic didn’t sit quietly. Shortly after WP Engine filed its lawsuit, Automattic filed its own counter-suit against WP Engine.
Automattic’s core claims included:
- Trademark infringement — Automattic alleged that WP Engine used the WordPress and WooCommerce trademarks in ways that confused consumers and violated Automattic’s trademark rights. Specifically, they pointed to WP Engine’s use of “WP” in its branding and marketing.
- Breach of contract — Automattic claimed WP Engine had agreed to certain trademark usage terms and then violated them.
- Unfair competition — related to how WP Engine positioned itself in relation to the WordPress brand without appropriate licensing or authorization.
Automattic’s position was essentially this: WP Engine built a billion-dollar business on the WordPress brand without properly licensing the trademarks it relied on. They argued WP Engine owed compensation for that use.
The trademark question is genuinely complex. The WordPress trademark is held by the WordPress Foundation, not Automattic. But Automattic manages trademark licensing on behalf of the Foundation. That layered structure creates real ambiguity about who has authority to enforce what, and how.
Both lawsuits were active and proceeding through the court system as of the time this post was written. The legal process will take time. Neither case is resolved quickly.
5. The WordPress.org Access Ban: What Mullenweg Actually Did
Here’s the part that alarmed the WordPress community most directly. And honestly, it’s the part that’s hardest to defend regardless of which side of the argument you’re on.
In the midst of the public dispute and legal filings, Mullenweg used his control over WordPress.org to block WP Engine’s access to specific WordPress.org resources.
What actually got blocked:
WP Engine’s sites and users temporarily lost access to certain WordPress.org services. WordPress.org is the central infrastructure for the open-source project. It hosts the official plugin repository, theme repository, and software updates that millions of WordPress sites depend on.
Mullenweg also moved control of the Advanced Custom Fields (ACF) plugin from its original developer, Elliot Condon, who worked at WP Engine, to WordPress.org. The plugin was rebranded as Secure Custom Fields under WordPress.org’s direct control.
ACF is one of the most widely used WordPress plugins in existence. Millions of WordPress sites depend on it. The move was controversial because it essentially removed a commercially developed plugin from a private company’s control and placed it under the open-source project’s control. The stated reason was a security dispute, but many in the community saw it as retaliation.
These actions sparked a massive debate about governance. Can one person, even the co-creator of WordPress, use infrastructure control to punish companies they disagree with? Should a platform that millions of businesses depend on be subject to one person’s commercial disputes?
The community hasn’t reached consensus. The debate is loud and ongoing.
6. The Trademark Issue: Who Really Owns WordPress?
The trademark question at the heart of the lawsuit deserves its own section. Because it’s genuinely complicated. And understanding it changes how you read the legal claims on both sides.
The WordPress trademark — the name “WordPress” itself — is owned by the WordPress Foundation. The Foundation is a nonprofit organization. Its stated mission is to preserve and protect WordPress as open-source software for public benefit.
Automattic manages trademark licensing on behalf of the Foundation under a licensing arrangement. That means Automattic, a for-profit company, effectively controls who can use the WordPress name commercially and under what terms.
This is a genuinely unusual arrangement. A nonprofit holds the trademark. A for-profit company managed by the same person who leads the nonprofit’s direction handles commercial enforcement. The lines between Automattic’s commercial interests and the WordPress Foundation’s public mission can get blurry fast.
WP Engine’s lawsuit argued that Automattic’s trademark enforcement actions against them were driven by commercial rivalry, not legitimate trademark protection concerns. They argued Mullenweg was weaponizing trademark control to serve Automattic’s business interests under the cover of open-source governance.
Automattic countered that WP Engine had been using the WordPress and WooCommerce brands in ways that genuinely misled users and violated agreed trademark terms.
Who’s right? The courts will decide. But the structural conflict of interest in how WordPress trademarks are managed is real regardless of how the lawsuit resolves. It’s something the WordPress community has to grapple with long after the legal dust settles.
7. What the WordPress Community Actually Thinks
The WordPress community is enormous. Millions of developers, designers, agencies, and business owners worldwide. And they are not unified on this situation.
The critics of Mullenweg and Automattic argue:
Using control over WordPress.org infrastructure to block a hosting company’s access was an abuse of power. The WordPress.org platform should be neutral infrastructure for the open-source community. Commercial disputes between Automattic and its competitors shouldn’t influence who gets access to the plugin repository or software updates.
Many long-time WordPress contributors expressed concern publicly. Several prominent community members resigned from official WordPress roles in protest. The governance question, specifically how much unilateral power one person should have over an open-source project used by hundreds of millions of websites, became a central community debate.
The defenders of Mullenweg’s position argue:
WP Engine genuinely built a massive commercial enterprise on the back of the WordPress community’s labor without contributing proportionally. The open-source social contract requires that companies profiting from the ecosystem give something meaningful back. Mullenweg forcing that conversation, even forcefully, was necessary and overdue.
They also point out that WP Engine is backed by private equity and operates primarily for profit. Expecting Automattic, which does employ significant numbers of WordPress core contributors, to be neutral toward a well-funded competitor free-riding on community infrastructure is unrealistic.
Both arguments have merit. That’s why the community is divided. And it’s why this situation matters beyond the courtroom.
8. The Broader Open-Source Ethics Question
The WordPress lawsuit raised a question that goes far beyond WordPress. It touches the fundamental tension at the heart of open-source software.
Open-source software is free to use, modify, and distribute. That freedom is the source of its incredible adoption and innovation. But it’s also the source of a persistent tension. Commercial companies can take open-source software, build profitable businesses on it, and technically owe nothing back to the community that created it.
Think of it like this. Imagine someone builds a market stall using timber from a community forest. The community made the timber available for free. The stall generates thousands of dollars a week. But the stall owner never plants a new tree or helps maintain the forest. Eventually, the forest has a problem.
That’s the economic tension Mullenweg was trying to force into the open. And it’s a real tension that exists across the open-source industry, not just in WordPress.
The question is whether one person’s aggressive public campaign and infrastructure pressure tactics were the right way to address it. Or whether it created more damage to the ecosystem than the free-riding problem ever did.
Different corners of the WordPress world answer that question differently. That disagreement will shape WordPress community governance for years to come, regardless of what the courts decide about specific legal claims.
9. What Happened to the Advanced Custom Fields Plugin?
The ACF plugin situation deserves a full explanation because it directly affected real WordPress users and developers.
Advanced Custom Fields is a plugin that lets developers add custom data fields to WordPress content. It’s used on millions of websites. Developers rely on it heavily for building custom themes, page templates, and complex content structures.
The plugin was originally developed by Elliot Condon, who later joined WP Engine. WP Engine owned the commercial version of ACF called ACF Pro.
In October 2024, amid the broader dispute, Mullenweg announced that WordPress.org was taking over the ACF plugin and renaming it Secure Custom Fields. The stated reason was that ACF’s update notices were being used to advertise commercial products, which violated WordPress.org plugin guidelines.
WP Engine and much of the community disputed this characterization. They saw it as retaliation. A privately developed plugin being effectively seized and rebranded under open-source project control is unprecedented in WordPress history.
What this means practically for developers:
- The free version of ACF is now maintained under the Secure Custom Fields name on WordPress.org
- WP Engine continues to develop ACF and ACF Pro independently
- Developers need to decide which fork to follow for future updates
- The plugin ecosystem’s stability as a whole took a confidence hit
Many developers were uncomfortable with the precedent. If WordPress.org can take control of a plugin during a commercial dispute, what does that mean for every other plugin built by companies in the ecosystem?
That question doesn’t have a clean answer yet.
10. Where the Lawsuits Stand Right Now
Legal proceedings move slowly. As of the time of writing this post, both lawsuits were proceeding through the court system.
Key developments:
WP Engine filed for a preliminary injunction shortly after filing its lawsuit. They asked the court to immediately stop Automattic from taking actions that disrupted WP Engine’s access to WordPress.org resources and damaged its business during the litigation.
Courts evaluate preliminary injunctions based on several factors. Whether the requesting party is likely to succeed on the merits of their case. Whether they’ll suffer irreparable harm without the injunction. Whether the balance of harms favors granting it. And whether the public interest is served.
Early hearings generated significant legal discussion about the trademark claims, the governance structure of WordPress.org, and Mullenweg’s dual roles as both Automattic CEO and WordPress.org’s effective controller.
The case is complex. Multiple causes of action across both suits. Trademark law, contract law, computer fraud statutes, and tortious interference claims all interacting. The full legal resolution could take years.
For businesses and developers using WordPress, the practical reality is that the platform is still running, still being developed, and still the world’s most popular CMS. The lawsuit affects the relationship between two large organizations at the top of the ecosystem. It doesn’t change how a well-built WordPress website functions day to day.
11. What This Means for Your WordPress Website
This is the question most business owners and website managers actually care about. Does the WordPress lawsuit affect your website?
The honest answer: not directly, right now.
WordPress as software continues to be developed, updated, and maintained. Core updates are still releasing on schedule. The plugin repository still has over 60,000 plugins. Themes are still available. Developers are still building on WordPress.
The lawsuit is between two organizations at the top of the commercial ecosystem. Your WordPress website doesn’t depend on WP Engine or Automattic being friendly with each other to function properly.
Where you might feel indirect effects:
If you host your website with WP Engine specifically, the dispute and its outcomes could affect how WP Engine operates, what it can offer, and potentially its business stability depending on legal outcomes.
If you use plugins developed or maintained by companies involved in the dispute, keep an eye on the ACF/Secure Custom Fields situation specifically. Knowing which version of the plugin you’re running and which branch is getting updates matters for long-term maintenance.
The governance uncertainty is worth watching. If the WordPress.org infrastructure becomes less neutral or less reliable due to ongoing disputes, it could affect plugin and update distribution over time.
Practical steps worth taking:
- Make sure your site’s plugins are up to date
- Know which hosting company manages your site and understand their stability
- Have a recent backup of your entire WordPress site right now, not later
- Work with a WordPress professional who tracks these developments and can advise you as the situation evolves
12. How WordPress Baba Helps You Navigate This Uncertainty
Situations like this are exactly why having a knowledgeable WordPress partner matters.
The WordPress lawsuit has raised real questions about platform governance, plugin reliability, and long-term ecosystem stability. Most business owners don’t have the time or background to track all of it. And they shouldn’t have to.
At WordPress Baba, this is what we watch so you don’t have to.
We stay on top of WordPress core developments, plugin ecosystem changes, and industry shifts that could affect our clients’ websites. When the ACF situation developed, we were advising clients immediately. When plugin updates have compatibility issues, we catch them before they become problems. When the ecosystem shifts, we adjust our recommendations.
Here’s what we do for the businesses that trust us:
We build WordPress websites on stable, well-tested foundations. We use plugins with strong community support and clear maintenance paths. We implement proper backup systems so no surprise development ever puts your site at serious risk. We monitor sites for security vulnerabilities so outdated software doesn’t become a door left open.
We also help businesses who are currently on hosting platforms caught up in this dispute evaluate their options. If you’re on WP Engine and feeling uncertain, we can give you an honest, unbiased assessment of whether moving makes sense for your specific situation.
The WordPress platform itself is not going anywhere. It’s too large, too widely used, and too deeply embedded in the internet’s infrastructure to collapse over a commercial dispute. But navigating the ecosystem smartly takes expertise.
That’s what we’re here for.
📞 Phone: +880 1886-465676 📧 Email: contact@wordpressbaba.com 🌐 Website: wordpressbaba.com
Conclusion
So, why is WordPress being sued?
The short version: WP Engine and Automattic are suing each other over trademark use, alleged extortion, access restrictions, and commercial fairness in the WordPress ecosystem.
Here’s what you actually need to remember:
Matt Mullenweg publicly attacked WP Engine in September 2024, accusing them of profiting from WordPress without contributing enough back. WP Engine sued Automattic and Mullenweg for extortion, trademark abuse, and interference with their business. Automattic counter-sued for trademark infringement. Mullenweg used control over WordPress.org infrastructure to restrict WP Engine’s access and took over the ACF plugin. The community divided sharply over whether these actions were justified or an abuse of power.
The case is still working through the courts. It will take time to resolve.
For your business and your website, the direct impact is limited right now. WordPress continues to function. But the governance questions this dispute raised matter for the long-term health of the open-source ecosystem millions of businesses depend on.
As the old saying goes: “When two elephants fight, it is the grass that suffers.” The WordPress community is watching carefully to make sure the grass recovers.
Stay informed. Keep your site updated. Work with people who understand the platform deeply.
If you need a WordPress partner who follows these developments and builds websites on solid, stable foundations, reach out to the team at WordPress Baba. We build for the long term.