Cyber Resilience

CVE-2026-63030

Wordpress 6.9 – 6.9.5

CISA KEVActive Exploitation
Published
17 July 2026
Modified
22 July 2026
KEV Added
21 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.98 99.9th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2026-63030 is a critical-severity Interpretation Conflict (CWE-436) vulnerability in Wordpress Wordpress. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

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…

more

Execution.

CWE(s)
CWE-436
KEV Date Added
21 July 2026

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

REST API route confusion enables remote exploitation of public-facing WordPress for SQLi leading to RCE.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
Direct exploitation of public-facing WordPress REST API endpoint enables initial compromise.
attack.mitre.org →
T1505.003 Web Shell Persistenceconfidence: HIGH
SQLi-to-RCE path in web application directly facilitates web shell deployment.
attack.mitre.org →
T1059.004 Unix Shell Executionconfidence: MEDIUM
RCE outcome enables arbitrary command execution via Unix/PHP shell on the server.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-60137Same product: Wordpress Wordpressboth on KEV
CVE-2023-22622Same product: Wordpress Wordpress
CVE-2024-31210Same product: Wordpress Wordpress
CVE-2023-5561Same product: Wordpress Wordpress
CVE-2023-2745Same product: Wordpress Wordpress
CVE-2024-4439Same product: Wordpress Wordpress
CVE-2024-31211Same product: Wordpress Wordpress
CVE-2023-38000Same product: Wordpress Wordpress
CVE-2016-10033Same product: Wordpress Wordpressboth on KEV
CVE-2026-9082Same product class: CMS coreboth on KEV

Affected Assets

wordpress
wordpress
6.9 — 6.9.5 · 7.0 — 7.0.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-10 Information Input Validation
  • AC-3 Access Enforcement
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely application of security-relevant patches, eliminating the REST batch endpoint route confusion and linked SQLi flaw by upgrading to fixed WordPress versions.

SI-10 Information Input Validation good match
prevent

Mandates validation of all inputs to the REST API batch endpoint, blocking the crafted author__not_in parameters that trigger the SQL injection.

AC-3 Access Enforcement partial match
prevent

Enforces access-control decisions on the WordPress REST API, limiting which users or unauthenticated callers can reach the vulnerable batch route.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly reduce the chance of introducing parser or state-machine inconsistencies.

DE.AE-03 partial match
prevents

Correlating logs from multiple products can surface discrepancies caused by interpretation conflicts.

DE.CM-09 partial match
prevents

Runtime monitoring of software behavior can detect adverse outcomes stemming from differing interpretations.

GV.SC-07 partial match
prevents

Supplier risk assessments can identify products whose differing interpretations create systemic exposure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect and correct cases where one component misinterprets another’s state or messages.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle can require consistent interface contracts and canonicalization rules that reduce interpretation conflicts between components.

A.8.26 Application security requirements partial match
prevents

Explicit application security requirements can mandate unambiguous protocol and data-format specifications that prevent divergent interpretations.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include well-defined component boundaries and shared data models that limit conflicting state perceptions.

A.8.28 Secure coding partial match
prevents

Secure coding standards can enforce canonical input handling and strict protocol compliance to avoid misinterpretation between products.

References