CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last KEV listing4d
- Last sighting47d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 21, 2026
- EUVDENISA, European Unionlisted Jul 21, 2026
- VulnCheck KEVcommercial researchlisted Jul 17, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 18, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
- reported exploitationapi.vulncheck.com/v3/index/vulncheck-canaries?cve=CVE-2026-6
59 public reports collected from VulnCheck and CIRCL, first on Jul 17, 2026. Each links to its original source. We have not verified them.
Description
WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
Required action (CISA)
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.






