CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2026-63030

WordPress Core Interpretation Conflict Vulnerability

WordPress Core

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.

CVSS

9.8

CRITICAL

EPSS

95.6%

30-day exploitation

Ransomware groups

recorded exploiting

Published

17 Jul 2026

CWE-436

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 21 July 2026. US federal agencies were required to remediate it by 24 July 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 95.6%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2026-63030 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2026-63030.

What does CVE-2026-63030 affect?

CVE-2026-63030 affects WordPress Core. 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.

How severe is CVE-2026-63030?

CVE-2026-63030 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 95.6%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 July 2026.

How should organisations respond to CVE-2026-63030?

Apply the vendor patch for WordPress Core as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.