← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-63030 exploited? Yes: in CISA KEV since 21 Jul 2026

Gociux · WordPress Core · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-63030, WordPress Core Interpretation Conflict Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 21 Jul 2026, 4 days after it was published. It affects WordPress Core. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 21 Jul 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity9.8CVSS 3.1 · critical
US federal due24 Jul 2026BOD 22-01 deadline

What it is

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.

VendorWordPress (7 exploited CVEs in KEV)
ProductCore
VulnerabilityWordPress Core Interpretation Conflict Vulnerability
WeaknessCWE-436
Published17 Jul 2026
Added to KEV21 Jul 2026
Reported by (CNA)WPScan

What to do

  1. Check whether you run it. Look for Core in your asset inventory, including appliances and cloud images. Stack check lists every exploited WordPress CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 17 Jul 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for WordPress.

Other exploited CVEs in Core

References

Questions

Is CVE-2026-63030 being exploited?

Yes. CISA added CVE-2026-63030 to the Known Exploited Vulnerabilities catalog on 21 Jul 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-63030 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-63030?

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. Check WordPress's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Core and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in July 2026 · WordPress scorecard · act-now radar.

Running WordPress in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →