KEV Lag Tracker → CVE-2026-60137. Data verified against the official CISA KEV catalog and the National Vulnerability Database.
CISA added CVE-2026-60137 (WordPress Core) to the Known Exploited Vulnerabilities catalog on July 21, 2026. It was publicly known for 4 days before CISA confirmed active exploitation. A KEV listing is CISA’s official confirmation that a vulnerability is being exploited in the wild.
The Record
| CVE | CVE-2026-60137 |
| Vendor / product | WordPress Core |
| Vulnerability | WordPress Core SQL Injection Vulnerability |
| CVSS base score | 5.9 |
| EPSS probability the day before the KEV listing | 4.03% (89.5% percentile) |
| NVD publication date | July 17, 2026 |
| Added to CISA KEV | July 21, 2026 |
| Lag (public → KEV listing) | 4 days |
| Federal patch deadline | August 4, 2026 |
| Known ransomware use | No |
Measured against the 1674 entries in our tracker with verified publication dates, CVE-2026-60137 was flagged faster than 79% of them.
What CISA Reported
CISA describes the flaw as follows: “WordPress Core contains a SQL injection vulnerability when a plugin or theme passes untrusted input to the parameter. This vulnerability can be chained with CVE-2026-63030 to allow an unauthenticated attacker to gain remote code execution on default WordPress installations.”
Federal Patch Deadline
Under Binding Operational Directive rules, U.S. federal agencies must remediate CVE-2026-60137 by August 4, 2026 — a 14-day remediation window from the KEV listing date. Private organizations are not bound by that deadline; CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.
What EPSS Forecast Before the Confirmation
The EPSS forecast (FIRST’s daily estimate of the probability a CVE will be exploited within 30 days) put CVE-2026-60137 at 4.03% on the day before CISA confirmed active exploitation — the 89.5% percentile of all scored CVEs that day. That places it outside the top 10% of EPSS risk on the eve of confirmation — a patch queue ordered by EPSS alone would have left it for later.
| EPSS for CVE-2026-60137 | Value |
|---|---|
| Probability the day before the KEV listing | 4.03% |
| Percentile the day before the KEV listing | 89.5% |
| Probability today (August 24, 2026) | 79.79% |
| Percentile today | 99.6% |
Today’s figure is not evidence that the forecast worked: EPSS reacts to the KEV listing itself, so the score for any confirmed-exploited CVE tends to rise after CISA acts. Only the eve-of-listing number was available to a defender making the call. Across every KEV entry we track, we measured how often that number was high — see the EPSS accuracy analysis.
How This Compares to WordPress’s Track Record
At 4 days, CVE-2026-60137 was flagged faster than WordPress’s 420-day median across the 5 of its KEV entries with verified publication dates. WordPress currently ranks #22 on our KEV Lag leaderboard.
| WordPress in the CISA KEV catalog | Value |
|---|---|
| Tracked KEV entries | 5 |
| Median lag (public → KEV listing) | 420 days |
| 0-day rate (exploited at or before disclosure) | 0% |
| Entries tied to known ransomware campaigns | 0 |
Other Recent WordPress KEV Additions
| CVE | Product | Added to KEV | Lag (days) | Ransomware |
|---|---|---|---|---|
| CVE-2026-63030 | Core | July 21, 2026 | 4 | No |
| CVE-2020-11738 | Snap Creek Duplicator Plugin | November 3, 2021 | 569 | No |
| CVE-2020-25213 | File Manager Plugin | November 3, 2021 | 420 | No |
| CVE-2019-9978 | Social Warfare Plugin | November 3, 2021 | 955 | No |
Defense guide: How to Detect SQL Injection: Attack Chain & Defense (2026) — detection signals, attack chain and response steps for this class of attack.
Frequently Asked Questions
What is CVE-2026-60137?
CVE-2026-60137 is a vulnerability in WordPress Core (WordPress Core SQL Injection Vulnerability) that CISA added to its Known Exploited Vulnerabilities catalog on July 21, 2026. A KEV listing is CISA’s official confirmation that the flaw is being exploited in the wild.
How long was CVE-2026-60137 public before CISA confirmed exploitation?
4 calendar days, measured from its NVD publication date to the date CISA added it to the KEV catalog.
What is the federal patch deadline for CVE-2026-60137?
U.S. federal agencies must remediate CVE-2026-60137 by August 4, 2026, a 14-day window from the KEV listing date. Private organizations are not bound by that deadline, but CISA treats it as the benchmark for how urgently a confirmed-exploited flaw should be patched.
Is CVE-2026-60137 used in ransomware campaigns?
CISA has not flagged CVE-2026-60137 as known to be used in ransomware campaigns. That field reflects confirmed campaign use, not the absence of risk.
What was the EPSS score for CVE-2026-60137 before it was confirmed as exploited?
4.03% — the probability EPSS assigned on the day before CISA added CVE-2026-60137 to the KEV catalog, placing it in the 89.5% percentile of all scored CVEs that day. That is outside the top 10% of EPSS risk. Its score today is higher in most cases because EPSS reacts to the KEV listing itself, so only the eve-of-listing figure reflects what a defender could have acted on.
How does this compare to other WordPress vulnerabilities?
Across 5 WordPress entries with verified publication dates, the median lag is 420 days and 0% were exploited at or before disclosure. CVE-2026-60137, at 4 days, is faster than that median.
Related Coverage
- WordPress’s CVE-2026-63030 Was Exploited in 4 Days — Well Under Its 420-Day Median (July 2026)
- Critical Microsoft SharePoint Flaw CVE-2026-50522 (CVSS 9.8) Added to CISA KEV (July 2026)
Primary Sources
- CISA Known Exploited Vulnerabilities Catalog — the official listing that confirms active exploitation, and the source of the KEV date on this page.
- NVD — CVE-2026-60137 — publication date, CVSS score and the full technical record.
- Vendor advisory — wordpress.org — WordPress’s own disclosure, with the affected versions and the fix.
How We Track This
This page is generated from our CISA KEV Lag Tracker, which syncs the official CISA KEV catalog daily and records the date each CVE is added. For every entry we retrieve the original NVD publication date and compute the lag in calendar days. No date or figure on this page is estimated or taken from a third-party source — they come directly from CISA and NVD records. Free to cite with attribution to CVEDaily (CC BY 4.0).