CVE-2026-60137
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
What it is
ReportedWordPress 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. Source description excerpt; complete tracked detail loads below.
NVD published: Jul 18, 2026 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026
What is affected
ReportedWordPress — Core. Product-level identification only; no affected-version conclusion is available from this field.
NVD published: Jul 18, 2026 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026
Urgency and basis
ReportedAct · 466.0
Tracker decision tier from the evidence detailed below · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026
Exploitation evidence
Reportedkev-listed · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog
CISA KEV added: Jul 21, 2026 · VulnCheck KEV added: Jul 17, 2026 · ENISA added: Jul 21, 2026 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026
What to do
ReportedApply 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.
Source remediation ↗Tracked source remediation field · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026
Evidence detail
Loading the full tracker evidence record…