Exploited CVEs / WordPress / CVE-2026-63030

CVE-2026-63030

WordPress Core Interpretation Conflict Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-07-24 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

CriticalCISA KEV

9.8

CVSS base

96%

EPSS exploit probability

Critical

Severity

2026-07-21

Added to KEV

2026-07-24 (past due)

CISA due date

Actively exploited WordPress Core vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-07-21.

Senserva AI read on CVE-2026-63030 CISA required action Official fix for CVE-2026-63030 Admin questions

Senserva AI Opinion for CVE-2026-63030

This is an interpretation conflict in WordPress Core that lets an attacker inject SQL and pivot to remote code execution, and it becomes far more dangerous when chained with CVE-2026-60137. Any site running WordPress Core is exposed, and with a 98 percent EPSS score plus confirmed exploitation on the CISA KEV list since 2026-07-21, attacks are already happening rather than theoretical. Because it touches the core rather than a single plugin, nearly every WordPress deployment is a potential target.

Do this: Update all WordPress Core installations to the patched version immediately and confirm CVE-2026-60137 is also addressed to break the exploit chain.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-63030

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2026-63030, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2026-63030.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-63030: WordPress Core Interpretation Conflict Vulnerability
- Affected: WordPress Core
- Severity: Critical, CVSS 9.8; EPSS 30-day exploitation probability 96%
- Added to CISA KEV: 2026-07-21; federal remediation due 2026-07-24
- Ransomware-linked: no
- CISA required action: 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 dis...
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Federal remediation deadline 2026-07-24; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-63030

Published: 2026-07-21
Last revised: 2026-07-21
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

The strongest signal is CVE-2026-63030's addition to the CISA KEV catalog on 2026-07-21, confirming active exploitation. Severity was set at 9.8 on 2026-07-23 as EPSS began at 38.6%, then climbed sharply to 97.9% by 2026-07-24 and peaked at 98.4% on 2026-07-30. It eased slightly to 95.6% by 2026-08-08, but remains critical. Patch today.

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

2026-07-21 added to the CISA KEV catalog by CISA
2026-07-23 CVSS 0.0 to 9.8; EPSS first scored at 38.6%
2026-07-24 EPSS 38.6% to 97.9%
2026-07-27 EPSS 97.9% to 98.0%
2026-07-30 EPSS 98.0% to 98.4%
2026-08-08 EPSS 98.4% to 95.6%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-07-24 (past due).

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.

Official fix for CVE-2026-63030

Check the vendor's security advisory channel for the patched Core versions and workarounds.

CISA KEV entry

Common questions about CVE-2026-63030

Is CVE-2026-63030 actively exploited?

Yes. CVE-2026-63030 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-07-21, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 96%.

What is the CISA deadline and required action for CVE-2026-63030?

CISA set the federal (BOD 22-01) remediation due date at 2026-07-24, which has passed; treat any unremediated system as overdue. The verbatim required action: 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.

What fixes CVE-2026-63030?

Check the vendor's security advisory for the patched Core versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-63030?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-63030's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited WordPress CVEs: CVE-2026-60137 CVE-2020-11738 CVE-2020-25213 CVE-2019-9978
All WordPress exploited CVEs on one page: WordPress vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.