Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious SQL payload in request parameter
-
DeliverySubmit to vulnerable PublishPress Revisions endpoint
-
ExploitExecute blind SQL injection query
-
ExecutionExtract sensitive database information
-
PersistIdentify admin credentials
-
ImpactCompromise WordPress installation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Remote unauthenticated attacker can exploit blind SQL injection in PublishPress Revisions plugin versions <= 3.7.23 through unspecified input parameter. No victim interaction required. Affects WordPress installations with vulnerable plugin enabled. |
| Impact | While CVSS and EPSS scores are unavailable for this CVE, the underlying risk is substantial. SQL injection vulnerabilities, particularly blind variants, typically carry high real-world exploitability due to automation potential and the foundational database access they provide. The affected software is a WordPress plugin with a broad deployment footprint, and the version range (through 3.7.23) suggests a relatively recent discovery. The lack of CVSS/EPSS scoring may indicate this is a newly disclosed vulnerability (CVE-2026 series) still undergoing formal assessment. The presence of Patchstack documentation and ENISA EUVD assignment (EUVD-2026-15913) confirms third-party validation. Exploitation likely requires low to medium attack complexity (crafting SQL payloads) and no authentication if the vulnerable parameter is exposed in unauthenticated endpoints. This should be treated as a high-priority vulnerability for any organization running PublishPress Revisions. |
| Exploit ScenarioDerived | An attacker identifies a vulnerable parameter in PublishPress Revisions' revision handling functionality and crafts a blind SQL injection payload, such as a time-based conditional query that pauses database response if a condition is true. By systematically iterating through character guesses and measuring response times, the attacker extracts sensitive data such as WordPress admin credentials, user email addresses, or plugin/theme configurations from the wp_users or wp_options tables. Once credentials are obtained, the attacker could escalate to full WordPress admin access and deploy malicious plugins or modify site content. No public proof-of-concept is confirmed in the available intelligence, but the straightforward nature of blind SQL injection exploitation suggests weaponizable exploits may be developed quickly. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
A blind SQL injection vulnerability exists in the PublishPress Revisions WordPress plugin through version 3.7.23, allowing attackers to execute arbitrary SQL commands against the underlying database. The vulnerability affects all installations of PublishPress Revisions up to and including version 3.7.23, enabling attackers to extract sensitive data, modify database contents, or potentially achieve remote code execution depending on database permissions and WordPress configuration. No CVSS score or EPSS data is currently available, and KEV status is unknown, though the vulnerability has been documented by Patchstack security researchers with a public reference available.
RemediationAI
Immediately upgrade PublishPress Revisions to a version above 3.7.23 if such a patched version is available from the PublishPress development team. Consult the Patchstack vulnerability database at https://patchstack.com/database/Wordpress/Plugin/revisionary/vulnerability/wordpress-publishpress-revisions-plugin-3-7-23-sql-injection-vulnerability and contact PublishPress directly for patch availability and release schedules. As an interim measure if patching is delayed, restrict access to PublishPress Revisions functionality via WordPress user role restrictions, disable the plugin if not actively required, and implement Web Application Firewall (WAF) rules to block common SQL injection patterns. Monitor WordPress database activity for suspicious queries, and review database user permissions to follow the principle of least privilege.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is classified as CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), which represents a failure to properly sanitize or parameterize SQL queries within the application. PublishPress Revisions, identified via CPE cpe:2.3:a:publishpress:publishpress_revisions:*:*:*:*:*:*:*:*, is a WordPress plugin that manages post revisions and versioning. The blind SQL injection variant indicates that attackers cannot directly observe query results in HTTP responses, requiring time-based or boolean-based inference techniques to extract data. The root cause stems from insufficient input validation or use of string concatenation instead of prepared statements when constructing SQL queries, a common WordPress plugin vulnerability pattern.
Know when Publishpress Revisions gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in PublishPress PublishPress Revisions revisionary allows Blind SQL Injection.This issue affects PublishPress Revisions: from n/a through <= 3.7.23.
Executive ViewAI
CVE-2026-32539 presents critical security risk, a SQL injection vulnerability rated CVSS 9.3. Successful exploitation could allow attackers to execute arbitrary code or commands on affected systems, potentially leading to full system compromise. Organizations should apply vendor updates immediately when available and implement compensating controls in the interim.
Apply vendor patch. If immediate patching is not feasible: (1) Deploy WAF rules to block injection patterns; (2) Restrict network access to affected components; (3) Enable enhanced logging for suspicious activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-15913
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB