Known exploited vulnerability · CISA KEV

CVE-2026-63030: WordPress Core Interpretation Conflict Vulnerability

WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.

CVE-2026-63030

Exploited in the wild. Fix this first.

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-07-21: attackers are using it right now.

CISA KEV: Listed; Added 2026-07-21 · federal fix-by 2026-07-24
EPSS (30 days): 11%; Higher than 96% of CVEs · 2026-11-01
CVSS v3.1: 9.8 Critical; CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What CISA says

WordPress Core Interpretation Conflict Vulnerability

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

NVD description · published 2026-07-17

WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.

Full record on NVD

Got a whole scan? Scan Hub runs this check on every finding in your Nessus, Qualys, Rapid7 or OpenVAS export and ranks the report by it.

Try it free

How to check if you are exposed to CVE-2026-63030

Find every WordPress Core system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2026-63030.

US federal agencies had to fix this by 2026-07-24. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.

Affected versions

Versions the National Vulnerability Database lists as vulnerable to CVE-2026-63030. Check the vendor advisory for the exact fixed builds before you sign anything off.

Product	Vulnerable versions
Wordpress	from 6.9 before 6.9.5; from 7.0 before 7.0.2

Timeline

2026-07-17 · Published in the National Vulnerability Database
2026-07-21 · Added to CISA's Known Exploited Vulnerabilities catalog, 4 days after it was published
2026-07-24 · Fix-by date for US federal agencies, passed 100 days ago

Vendor advisories and fixes

https://wordpress.org/news/2026/07/wordpress-7-0-2-release/

Weakness type

CWE-436

More exploited WordPress vulnerabilities

CISA lists 6 exploited WordPress vulnerabilities. The closest matches:

Keep going

Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.