Threat Intelligence / CVE / CVE-2026-63030

CVE-2026-63030 — WordPress

CISA KEV
CVSS v3.1 9.8 (CRITICAL) · EPSS 38.5% (higher than 98.4% of all scored CVEs) · Priority 9/10 · Published 2026-07-17

As of 2026-07-22, CVE-2026-63030 is a CRITICAL-severity vulnerability in WordPress, CVSS v3.1 9.8, EPSS 38.5% (98.4th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-07-21), with a US federal remediation deadline of 2026-07-24. Threadlinqs Intelligence links 4 tracked threat campaigns to CVE-2026-63030, most recently “AI-Agent-Driven Offensive Operation: Mass Cryptocurrency Wallet and Credential Compromise via Autonomous AI Coding Agents”.

Last updated: 2026-07-22

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.

The record classifies CVE-2026-63030 under weakness class CWE-436. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 57 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
38.5% probability of exploitation in the next 30 days, higher than 98.4% of all scored CVEs
CISA KEV
Listed since 2026-07-21, federal remediation deadline 2026-07-24
Threadlinqs priority
9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published
2026-07-17, last modified 2026-07-22

Is CVE-2026-63030 being exploited?

CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 2026-07-21, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-07-24 under BOD 22-01. Weaponised exploit code for CVE-2026-63030 is publicly available. 10 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2026/CVE-2026-63030.yaml). It currently carries a trending score of 73 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-63030

Vendor advisory: https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662q. Because CVE-2026-63030 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-07-24. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-63030

4 tracked threats in the Threadlinqs corpus reference CVE-2026-63030, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Technical analysis

Full detection coverage & IOCs for threats exploiting CVE-2026-63030 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence