Known exploited vulnerability
CVE-2026-63030
WordPress Core Interpretation Conflict Vulnerability
What happened
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.
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.
Analyst notes
https://wordpress.org/news/2026/07/wordpress-7-0-2-release/ ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-63030
Public proof-of-concept repositories
No matching public repository was found in the scheduled GitHub index. The index refreshes every 30 minutes; a result would be an unverified repository mention, not a safety assessment.
More from WordPress
- CVE-2026-119977 WordPress WordPress Core Time-of-check Time-of-use (TOCTOU) Race Condition Vulnerability
- CVE-2026-87902 WordPress Core Remote File Inclusion Vulnerability
- CVE-2026-60137 WordPress Core SQL Injection Vulnerability
- CVE-2020-25213 WordPress File Manager Plugin Remote Code Execution Vulnerability
- CVE-2020-11738 WordPress Snap Creek Duplicator Plugin File Download Vulnerability
- CVE-2019-9978 WordPress Social Warfare Plugin Cross-Site Scripting (XSS) Vulnerability