CVE-2026-63030

CVE-2026-63030 is a critical-severity vulnerability in Wordpress with a CVSS 3.x base score of 9.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2026-07-21). The underlying weakness is classified as CWE-436.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-63030?
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 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-63030 being actively exploited?
Yes. CVE-2026-63030 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2026-07-21, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2026-63030?
CVE-2026-63030 affects Wordpress. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-63030?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
When was CVE-2026-63030 published?
CVE-2026-63030 was published on 2026-07-17 and last updated on 2026-07-22.

References

Affected products (1)

More vulnerabilities in Wordpress

All CVEs affecting Wordpress →

Other CWE-436 vulnerabilities

Browse all CWE-436 vulnerabilities →