CVE-2026-63030KEV · OVERDUECWE-436

WordPress Core Interpretation Conflict Vulnerability

Critical · published July 18, 2026

Patch now

Confirmed exploited, and the score agrees

CVSS calls it critical at 9.8. It is confirmed in active exploitation. It sits in the 95.8th percentile for exploit probability.

92
days past CISA
deadline
CVSS v3.1
9.8
EPSS
11%
Percentile
95.8
In the wild
Confirmed
Chains
1
What it is

🚨 A sneaky route confusion in WordPress could unleash chaos! Just two vulnerabilities combined allow attackers to execute SQL injections and gain remote code execution. 🔥 Think of it like a postal service misrouting packages — the delivery person has no idea where to send the important documents, leading to potentially sensitive info landing in the wrong hands. That's exactly how attackers can exploit this REST API issue! An attacker could infiltrate your WordPress site, execute arbitrary code, and wreak absolute havoc — think stolen data, defaced pages, or even complete server takeover. The potential for damage is absolutely devastating, making this a critical situation!

Put simply

Think of it like a postal service misrouting packages — the delivery person has no idea where to send the important documents, leading to potentially sensitive info landing in the wrong hands. That's exactly how attackers can exploit this REST API issue! The CVE-2026-63030 vulnerability in WordPress stems from a REST API batch endpoint route confusion issue. This flaw, when combined with the author__not_in WP_Query SQL Injection vulnerability, allows attackers to manipulate SQL queries and run arbitrary commands on the server.

Part of a larger chain

CVE-2026-63030's CNA description states the REST API batch endpoint route confusion is exploitable "combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137)".

CVE-2026-60137SQL injection · 5.9
CVE-2026-63030Interpretation conflict · 9.8
Remote code executionFull site compromise
What to do

An attacker could infiltrate your WordPress site, execute arbitrary code, and wreak absolute havoc — think stolen data, defaced pages, or even complete server takeover. The potential for damage is absolutely devastating, making this a critical situation! Immediately update WordPress to version 6.9.5 or 7.0.2 to patch this vulnerability. It’s also a good idea to audit your plugins and themes for any outdated components that may exacerbate the risk. Ensure you have robust security measures in place! You've got this! Follow these steps, and you'll lock down your site in no time. 🛡️

The record
Technical detail
CVSS v3.1
9.8 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.10649 · 95.8th percentile
Weakness
CWE-436 · Interpretation Conflict
Published
2026-07-18T00:17Z
KEV added
2026-07-21 · due 2026-07-24
Affected products (2)
ProductVersionsFixed in
wordpress/wordpress≥ 6.9, < 6.9.56.9.5
wordpress/wordpress≥ 7.0, < 7.0.27.0.2
References (3)
EPSS history
Timeline
  • 25 SEP 03:26Z
    EPSS moved 97% → 10%
    epss
  • 21 JUL 00:00Z
    Added to CISA KEV — remediate by Jul 24
    kev
  • 17 JUL 19:14Z
    WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code Execution
    cvelistv5