{"id":45156,"date":"2026-04-07T02:29:46","date_gmt":"2026-04-06T18:29:46","guid":{"rendered":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/07\/cloudflare-targets-wordpress-with-new-ai-powered-emdash-cms\/"},"modified":"2026-04-07T02:29:46","modified_gmt":"2026-04-06T18:29:46","slug":"cloudflare-targets-wordpress-with-new-ai-powered-emdash-cms","status":"publish","type":"post","link":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/07\/cloudflare-targets-wordpress-with-new-ai-powered-emdash-cms\/","title":{"rendered":"Cloudflare Targets WordPress With New AI-Powered EmDash CMS"},"content":{"rendered":"\n

Technology and website security giant Cloudflare<\/a> has launched EmDash CMS, a new content management system designed to challenge the dominance of WordPress. While WordPress currently powers over 40% of the internet, Cloudflare researchers noted that the 24-year-old platform is struggling with a “security crisis” that leaves millions of sites at risk.<\/p>\n

Ending the plugin crisis<\/strong><\/h3>\n

The move is a direct response to the massive safety risks found in traditional website add-ons. According to Cloudflare\u2019s announcement<\/a> of the new system, around 96% of WordPress security issues<\/a> start within its plugins. In 2025, the number of high-severity flaws in the ecosystem actually surpassed the total from the previous two years combined.<\/p>\n

The problem lies in how these tools are built, as researchers noted that most WordPress plugins use PHP<\/a> and have total access to a site\u2019s database. EmDash, however, uses a sandbox method where every plugin runs in its own isolated space, known as a Dynamic Worker. This means a plugin can only do exactly what it declares in a manifest file, such as a specific email:send<\/code> permission, and cannot touch other parts of the website.<\/p>\n

Built for the AI era<\/strong><\/h3>\n

EmDash was developed in just two months using AI coding agents and is written entirely in TypeScript. It is powered by Astro, a framework built for speed, and uses serverless technology<\/a>. This allows a site to “scale to zero,” which means it stays dormant and costs nothing until a visitor arrives, rather than needing a server running 24\/7.<\/p>\n

The system also prepares creators for a future dominated by AI. It features Agent Skills and a built-in Model Context Protocol (MCP<\/a>) server, allowing AI assistants to manage the site or help move old WordPress themes over. Moreover, it includes a payment layer called x402, which uses an “HTTP 402 Payment Required” code to let owners charge automated AI bots for reading their content. To prevent unauthorised access, it ditches passwords entirely, using Passkeys by default.<\/p>\n

\n
\"Cloudflare<\/a>
EmDash\u2019s built-in business model (Image source: Cloudflare)<\/figcaption><\/figure>\n<\/p><\/div>\n

A war of words<\/strong><\/h3>\n

The launch has already sparked a row with WordPress co-founder Matt Mullenweg. On 2 April 2026, Mullenweg hit back, suggesting “EmDash was created to sell more Cloudflare services.” He argued in his response blog post<\/a> that the unrestricted power of WordPress plugins is actually a feature and noted that WordPress remains more flexible because it can run on anything from a Raspberry Pi <\/a>to a massive data centre.<\/p>\n

While Mullenweg admitted EmDash\u2019s engineering was “very solid,” he claimed a true successor should be “even more open.” Despite the criticism, Cloudflare has released the v0.1.0 preview as an open-source project under the MIT license on GitHub. For those looking to switch, a new migration tool can, reportedly, move an entire WordPress site over in just a few minutes.<\/p>\n

\n
\"Cloudflare<\/a>
WordPress and EmDash Comparison (Image source: Cloudflare)<\/figcaption><\/figure>\n<\/p><\/div>\n

Whether EmDash CMS can truly challenge WordPress is still an open question, but Cloudflare is clearly betting that security, automation, and AI-ready infrastructure will matter more than backward compatibility and plugin freedom. Nevertheless, it comes down to a choice between flexibility and control, openness and tighter security, or sticking with what works versus moving to a system built for how the web is starting to operate. <\/p>\n