CVE-2026-63030 — WordPress Core | CVSS 9.8 CRITICAL

CRITICAL

CVSS 9.8 CRITICAL  ·  EPSS 9%  ·  WordPress Core

Severity Overview

Summary

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.

What the Attack Looks Like

If successfully exploited: A successful exploit gives the attacker code execution in the context of the victim’s user session, enabling credential theft, malware installation, or lateral movement from the endpoint. Full confidentiality and integrity impact means an attacker can both read and modify sensitive data — useful for credential harvesting, data theft, or manipulating application state. High availability impact means the vulnerability can also cause a denial of service, which may be used for disruption or as a diversion during a broader attack. The lateral movement potential mapped to T1210 means an attacker who gains initial access through this CVE may be able to spread to adjacent systems before detection.

Analyst Takeaway

The attack is launched over the network (remotely exploitable without physical access) and no authentication is required. This vulnerability is already in CISA KEV, which means exploitation has been confirmed in the wild — treat this as active risk, not theoretical exposure. The CVSS score places this in critical territory, so internet-facing systems and high-value assets should be prioritized for immediate remediation or compensating controls. Because the mapping suggests remote service exploitation potential, defenders should also consider post-compromise lateral movement scenarios during investigation. In parallel with patching, defenders should review external exposure, hunt for signs of exploitation, and validate whether compensating controls are in place for vulnerable assets.

MITRE ATT&CK Mapping

• T1203 – Exploitation for Client Execution
  Rationale: The vulnerability appears tied to a client application such as a browser, document handler, or end-user productivity software.
• T1210 – Exploitation of Remote Services
  Rationale: The vulnerability context suggests exploitation of services commonly used for remote access or lateral movement.

Detection Guidance

• T1203 — Exploitation for Client Execution
  • Inspect endpoint telemetry for suspicious execution chains: scripting engines or download utilities launched as children of browsers, Office applications, PDF readers, or other client-side software.
  • Look for LOLBin usage (certutil, mshta, rundll32, regsvr32, wmic) with suspicious arguments spawned from document-handling parent processes.
  • Review email attachment and file download activity correlated with any suspicious process execution on the same endpoint within the same time window.
• T1210 — Exploitation of Remote Services
  • Monitor SMB, RDP, WinRM, SSH, and RPC activity between internal systems for patterns outside your normal management baseline.
  • Look for authentication bursts: repeated failures (Event ID 4625) from the same source followed by a successful logon (Event ID 4624).
  • Investigate remote execution behavior and lateral movement artifacts (PsExec, WMI remote execution, remote scheduled task creation) originating from recently exposed assets.

Hunting Considerations

These are proactive hunts mapped to the ATT&CK techniques identified for this CVE. Run them now — do not wait for an alert to fire.

• T1203 — Exploitation for Client Execution
  • Parent-child process chains: Search for scripting engines (PowerShell, cmd.exe, wscript.exe, cscript.exe, mshta.exe) or download utilities (certutil, bitsadmin, curl) spawned as direct children of Office applications, browsers, or PDF readers. These chains are rarely legitimate.
  • LOLBin execution: Hunt for Living-off-the-Land Binaries — regsvr32, rundll32, mshta, certutil, wmic, odbcconf — executing from unusual working directories or with command lines containing encoded strings, remote paths, or -enc / -nop / IEX patterns.
  • Network connections from client apps: Flag outbound connections to new external IPs from browser, Office, or document-handling processes that do not match known CDN or update infrastructure. These indicate the exploited process reaching out for a secondary payload.
  • Windows Event IDs: Event 4688 (process creation with full command line) and Sysmon Event 1 are your primary sources. Filter for suspicious parent-child pairs. Sysmon Event 3 (network connection) from document handlers is a high-fidelity indicator.
  • Correlation with delivery: Check email gateway and proxy logs for attachment opens or file downloads on the same host in the 30 minutes before any suspicious process execution — this helps confirm the initial delivery vector.
• T1210 — Exploitation of Remote Services
  • Authentication burst pattern: Hunt for Event ID 4625 (failed logon) followed quickly by Event ID 4624 (successful logon) from the same source IP. This burst — repeated failures then success — is a classic exploitation indicator. Flag unusual Logon Type values: Type 3 (network), Type 10 (RemoteInteractive).
  • Unexpected east-west traffic: Look for new SMB (445), RDP (3389), WinRM (5985/5986), or SSH (22) connections between internal hosts that do not follow normal patterns — especially from workstations to servers or from servers outside your known management tooling.
  • Lateral movement artifacts: Hunt for PsExec service entries (Event ID 7045 with service name “PSEXESVC”), WMI remote execution (wmiprvse.exe spawning child processes), and scheduled tasks created via remote sessions (Event ID 4698).
  • Segmentation gaps: Confirm which affected hosts have network paths to domain controllers, file servers, or databases. Remote service exploitation is substantially more dangerous when segmentation is absent — validate this before concluding triage.
  • Unusual ports: Some exploitation of remote services uses non-standard ports. Cross-reference all new internal connections against your expected service port baseline to catch off-port lateral movement.

Recommended Actions

Immediate (0–24 Hours)

• Inventory: Identify all systems running WordPress Core. Include production, staging, dev, and cloud environments — untracked instances are the most likely to remain unpatched.
• Validate internet-facing exposure: Determine which of the affected systems are reachable from the public internet. Prioritize these for immediate remediation or compensating controls.
• Apply compensating controls now: For systems that cannot be patched immediately, implement temporary mitigations: restrict access via firewall rules or ACLs, add WAF rules if applicable, disable or isolate the vulnerable component if feasible without breaking critical operations.

Remediation

• Apply the vendor patch: 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.
• CISA directive deadline: 2026-07-24 — this is the mandatory deadline for US federal civilian agencies under BOD 22-01. All organizations should treat this date as a strong target regardless of federal mandate.
• Verify remediation: After patching, confirm the correct version is installed on all affected hosts. Run a vulnerability scan or use your asset management tooling to verify — do not rely solely on change tickets.
• Post-patch compromise assessment: Privilege escalation and lateral movement techniques can result in persistent access that survives patching. After remediation, review the hunting considerations in this alert to assess whether compromise occurred before the patch was applied.

Detection Coverage

• Verify ATT&CK coverage: Confirm your SIEM and EDR have detection logic in place for T1203, T1210. Review the Detection Guidance and Hunting Considerations sections of this alert for the specific log sources and behavioral patterns to monitor.
• Unauthenticated exploitation monitoring: Because this vulnerability requires no authentication, internet-facing scanning and exploitation attempts may begin within hours of public disclosure. Ensure alerting is in place before the end of the day.
• Threat intelligence feeds: Monitor your TI feeds and vendor advisory channels for published indicators of compromise (IOCs), proof-of-concept exploit releases, or active campaign reporting associated with this CVE — these should trigger an immediate hunt even if no internal alerts have fired.

Detection Playbooks

Vulnerability Details

Additional Notes

https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-63030