Exploited CVEs / WordPress / CVE-2026-60137
CVE-2026-60137
WordPress Core SQL Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-08-04 (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
Actively exploited WordPress Core vulnerability, Medium severity, CVSS 5.9. Added to the CISA KEV catalog 2026-07-21.
Senserva AI Opinion for CVE-2026-60137
This WordPress Core SQL injection is rated Severity Medium (CVSS 5.9), but the numbers around it tell a different story: it is on CISA KEV as of 2026-07-21 with a 78% EPSS score, and it chains with CVE-2026-63030 to give unauthenticated attackers remote code execution on default installs. Any WordPress site is exposed, and the low base score understates the real risk once the chain is used.
Do this: Update WordPress Core to the patched version now and confirm CVE-2026-63030 is also remediated 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-60137
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2026-60137
- 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.
The strongest signal is the CISA KEV listing on 2026-07-21, confirming active exploitation. Severity was set on 2026-07-23 at 5.9, while EPSS started at 20.4% and jumped to 78.0% by 2026-07-24, peaking at 79.0% on 2026-07-30 before easing to 73.1% on 2026-08-08. Exploitation likelihood remains high, so prioritize patching 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 5.9; EPSS first scored at 20.4%
- 2026-07-24 EPSS 20.4% to 78.0%
- 2026-07-30 EPSS 78.0% to 79.0%
- 2026-08-08 EPSS 79.0% to 73.1%
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-08-04 (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-60137
Check the vendor's security advisory channel for the patched Core versions and workarounds.
Common questions about CVE-2026-60137
Is CVE-2026-60137 actively exploited?
Yes. CVE-2026-60137 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 73%.
What is the CISA deadline and required action for CVE-2026-60137?
CISA set the federal (BOD 22-01) remediation due date at 2026-08-04, 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-60137?
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-60137?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-60137'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
All WordPress exploited CVEs on one page: WordPress vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.