Security readout for executives and security teams
Plain-English summary
This vulnerability affects recent WordPress 6.9.x and 7.0.x installations before fixed releases. An unauthenticated attacker could combine REST API route confusion with a related SQL injection to reach remote code execution. For public WordPress sites, this is an urgent patching issue.
Executive priority
Treat this as emergency remediation for exposed WordPress assets. The combination of unauthenticated network access, possible remote code execution, and KEV status creates material compromise risk if patching is delayed.
Technical view
The issue is described as REST API batch endpoint route confusion in WordPress, chained with CVE-2026-60137 in WP_Query author__not_in handling. The reported impact is SQL injection leading to remote code execution. CVSS is 9.8, network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Internet-facing WordPress sites running 6.9.x before 6.9.5 or 7.0.x before 7.0.2 are the primary exposure. The bundle lists WordPress 6.9.0 and 7.0.0 as affected examples, with default status otherwise unaffected.
Exploitation context
The bundle marks CVE-2026-63030 as present in CISA KEV, supporting known exploitation. No campaign details, exploit maturity, indicators, or proof-of-concept information are included in the provided sources.
Researcher notes
Evidence is limited to the supplied CVE bundle, GitHub advisory reference, WordPress release note reference, and CISA KEV reference. The bundle identifies CWE-436 and the dependency on CVE-2026-60137, but provides no safe validation payloads or detailed exploit chain.
Mitigation direction
- Upgrade affected WordPress 6.9.x sites to 6.9.5 or later.
- Upgrade affected WordPress 7.0.x sites to 7.0.2 or later.
- Prioritize public, high-traffic, and business-critical WordPress installations.
- Review vendor advisory and release notes before applying compensating controls.
- Monitor WordPress logs for suspicious REST API activity.
Validation and detection
- Inventory WordPress core versions across production and staging sites.
- Confirm no site remains on 6.9.0 through 6.9.4.
- Confirm no site remains on 7.0.0 or 7.0.1.
- Verify patch deployment through WordPress admin, package inventory, or file integrity tooling.
- Check whether vulnerability scanners recognize CVE-2026-63030 after updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-436: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-63030 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WPScanCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2026-63030 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-07-21T00:00:00.000Z: CVE-2026-63030 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662qCVE reference, WPScan · vdb-entry, technical-description
- https://wordpress.org/news/2026/07/wordpress-7-0-2-release/CVE reference, WPScan · release-notes, vendor-advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-63030CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Interpretation Conflict
Interpretation Conflict represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.