SAK T.E.CTechnology · Evaluation · Compliance Free domain checkCheck

Exploited vulnerabilities / CVE-2026-63030

Confirmed exploited · remote code execution · WordPress Core

CVE-2026-63030

WordPress Core remote code execution, confirmed exploited in the wild.

WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.

11%chance of exploitation in the next 30 days (EPSS), 95th percentile
21 Juladded to CISA's Known Exploited Vulnerabilities list, 2026
24 Julfederal remediation deadline, already passed
Passedpast the deadline: patch now
CISA's name for itWordPress Core Interpretation Conflict Vulnerability
Vendor and productWordPress · Core
Typeremote code execution · CWE-436
ExploitedConfirmed by CISA listed 21 July 2026
Likelihoodone of the most likely to be exploited of every vulnerability tracked
Deadline24 July 2026 · already passed
Used in ransomwareNot reported
Advisorieswordpress.org ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗
What to do

Three steps, in this order

Step 1

Patch to the fixed version the vendor names, today if the product faces the internet.

Step 2

Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.

Step 3

Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

CISA's required actionApply 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.
Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Questions

CVE-2026-63030 in short

Is CVE-2026-63030 being exploited?

Yes. CISA added CVE-2026-63030 to its Known Exploited Vulnerabilities catalogue on 21 July 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-63030?

US federal agencies must remediate it by 24 July 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-63030 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 11%, the 95th percentile of every CVE it scores.

How do I fix CVE-2026-63030?

Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.

Same vendor

Other WordPress vulnerabilities being exploited

CVEProductTypeListed
CVE-2026-119977WordPress Coreexploited vulnerability3 November 2026
CVE-2026-87902Coreremote code execution25 September 2026
CVE-2026-60137Coreremote code execution21 July 2026

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.

Chat with us