These vulnerabilities represent a critical risk to the massive WordPress ecosystem, allowing unauthenticated attackers to execute code or manipulate databases. Cloudflare's proactive WAF deployment provides a vital safety net while automated and manual patching processes take place.
Cloudflare has deployed new Web Application Firewall (WAF) protections for two critical vulnerabilities affecting WordPress. The protections address an Unauthenticated Remote Code Execution (RCE) vulnerability in WordPress's REST API and a related SQL Injection vulnerability.
The WordPress security team disclosed the vulnerabilities to Cloudflare before public release so that we could prepare protections for customers. Cloudflare has deployed the new rules to protect all customers, including those on free and paid plans, as long as their application traffic is proxied through the Cloudflare WAF. The rules were deployed at 17:03 UTC on July 17 2026.
WAF protections reduce exposure while customers update, but they are not a substitute for patching. WordPress has released fixes in version 7.0.2, with backports to affected earlier branches: 6.9.5, 6.8.6, and 7.1 Beta 2 (see release details). Versions earlier than 6.8 are not affected. WordPress is treating this as its highest-severity, highest-priority class of issue and is forcing automatic updates to affected sites, so most sites will be updated automatically. We still recommend confirming that you are on a patched release or the backports for your branch and follow the guidance in the official WordPress security release announcement.
The vulnerabilities affect different parts of the request path:
The SQL injection vulnerability is present from version 6.8 onwards, while the RCE only affects versions from 6.9. So 6.8.6 addresses the SQLi only since the RCE isn't present on 6.8, while 6.9.5, 7.0.2, and 7.1 Beta 2 get fixes for both.
Cloudflare created two rules to detect requests associated with these vulnerabilities:
Cloudflare customers running WordPress sites on Pro, Business, or Enterprise plans should ensure that Cloudflare Managed Rules are enabled. Customers can follow the steps in our WAF Managed Rules documentation. Customers on free plans are automatically protected through the Free Ruleset.
The new rules are deployed with the default Managed Ruleset action of Block. Customers running WordPress sites should review any ruleset-level overrides, including those that change all rules from Block to Log, and ensure the new rules use the recommended action while they update WordPress. Cloudflare customers should also monitor Security Events for requests matching either rule.
The SQL injection rule detects crafted parameter values before they reach WordPress. The unauthenticated RCE rule targets requests attempting to reach the remote code execution path. Together, they detect the attack at two different points.
These rules reduce risk while organizations update affected systems; they do not fix the underlying vulnerable code. Updating WordPress remains the most effective way to address the vulnerabilities.
If an immediate update is not possible, verify that both Cloudflare rules are active with the recommended action and review logs for suspicious requests to the affected REST API endpoint.
Cloudflare will monitor matching traffic and test the rules against new attack variations, updating detections when needed.
We thank the WordPress security team for coordinating with Cloudflare and other infrastructure providers to help protect users before details of the vulnerabilities became public.
Continue reading on the original blog to support the author
Read full articleAnalyzing global internet disruptions helps engineers understand the impact of physical infrastructure, geopolitical interference, and configuration errors on system availability, emphasizing the need for redundancy and resilient routing in distributed architectures.
Debugging privacy protocols like OHTTP is notoriously difficult due to multi-party interactions and binary encoding. pvcli streamlines this by automating encryption and protocol steps, significantly reducing the time spent on manual bit-level analysis and incident response.
Debugging privacy protocols is difficult due to multi-party interactions and binary encoding. pvcli reduces friction by automating cryptographic steps and binary parsing, allowing engineers to diagnose issues across relays and gateways in seconds rather than hours.
BGP ORIGIN manipulation undermines the predictability of global routing. With 70% of paths modified to attract traffic, engineers can't rely on standard protocol behavior for traffic engineering, leading to suboptimal paths and potential security or performance issues.
