Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber WordPress account
-
DeliveryAuthenticate to target WordPress site
-
ExploitIdentify vulnerable WP Project Manager Pro plugin endpoint
-
ExecutionSend crafted HTTP request with SQL injection payload
-
PersistExtract full WordPress database contents
-
ImpactRetrieve and crack administrator password hashes
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 | Exploitation requires a valid subscriber-level (or higher) WordPress user account on the target site. Subscriber is the lowest registered user role in WordPress; sites with open user registration - the default on many WordPress installations - allow any unauthenticated internet user to self-create this account, effectively lowering the barrier to near-unauthenticated. No special plugin feature, configuration setting, or non-default deployment mode is required beyond having WP Project Manager Pro active at version <= 4.0.1. What limits exploitation: the attacker must possess at minimum a valid WordPress login for the target site, and sites that have explicitly disabled user registration with no other account-creation pathway reduce the exposed population significantly. The CVSS I:N suggests write capability is not confirmed from available data, limiting confirmed impact to data exfiltration. |
| Impact | The CVSS 8.5 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L) reflects a network-exploitable SQL injection requiring only subscriber-level access - the lowest registered WordPress user role - with low attack complexity and no user interaction required. The scope change paired with High confidentiality impact suggests the injection enables full cross-table database reads, including administrator password hashes and any sensitive data stored by co-installed plugins. EPSS data was not provided, so exploitation probability cannot be numerically quantified, and no KEV listing means active exploitation is not confirmed. However, the extremely low privilege barrier - many WordPress sites enable open user registration by default, allowing any anonymous internet user to obtain a subscriber account - meaningfully elevates real-world risk beyond what the PR:L metric alone suggests. The integrity impact of N in the provided CVSS vector warrants verification: depending on the MySQL user permissions and whether stacked queries are supported, read-only SQLi sometimes permits writes in practice. The absence of a confirmed patched version number in available intelligence is a gap that defenders must close by checking the Patchstack advisory directly. |
| Exploit ScenarioDerived | An attacker self-registers a subscriber account on a WordPress site running WP Project Manager Pro 4.0.1 or earlier - a trivial step on any site with open registration - then sends a crafted authenticated HTTP request containing a SQL injection payload to a vulnerable plugin endpoint. The injected query reads the wp_users table to extract administrator password hashes and email addresses, which are then cracked offline or used to escalate to full WordPress admin access. No public exploit code has been identified at time of analysis, but the low complexity and broad availability of WordPress SQLi techniques make independent development straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
SQL Injection in WP Project Manager Pro versions 4.0.1 and below allows authenticated subscriber-level users to execute arbitrary SQL queries against the WordPress database, potentially exposing the full database contents including credentials and sensitive user data. The vulnerability carries a CVSS 8.5 (High) with scope change, meaning exploitation reaches beyond the plugin itself to the underlying WordPress database. Reported by Patchstack and tracked as EUVD-2026-64802; no active exploitation (CISA KEV) has been confirmed, and no public exploit code has been identified at time of analysis.
RemediationAI
Update WP Project Manager Pro to a version above 4.0.1 as soon as a patched release is confirmed by the vendor; consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wedevs-project-manager-business/vulnerability/wordpress-wp-project-manager-pro-plugin-4-0-1-sql-injection-vulnerability for the confirmed fix version, which was not specified in the available intelligence. As an immediate compensating control, disable open WordPress user registration (Settings > General > uncheck 'Anyone can register') to eliminate the path by which anonymous users can obtain the subscriber role required for exploitation - note this will block legitimate self-registration flows. Additionally, a WordPress-aware WAF rule targeting SQL metacharacters in plugin endpoint parameters can reduce exploitation success during the patching window, though WAF rules should not substitute for the patch. Audit WordPress user accounts for unexpected subscriber registrations as an indicator of potential prior exploitation attempts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WP Project Manager Pro (CPE: cpe:2.3:a:wedevs_pte._ltd:wp_project_manager_pro) is a premium WordPress project management plugin by weDevs Pte. Ltd. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), where user-supplied input from subscriber-level authenticated requests is incorporated into database queries without adequate sanitization or use of parameterized prepared statements. The CVSS scope change (S:C) indicates the injection allows access beyond the plugin's own data scope to the broader WordPress database, which may include wp_users, custom tables from other plugins, and any other data stored in the shared MySQL/MariaDB instance underlying the WordPress installation.
Know when Wp Project Manager Pro 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:L/UI:N/S:C/C:H/I:N/A:L
Network-accessible plugin endpoint requiring only subscriber auth (PR:L); scope change reflects cross-table DB read beyond plugin boundary; no confirmed write impact justifies I:N.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber SQL Injection in WP Project Manager Pro <= 4.0.1 versions.
Executive ViewAI
WP Project Manager Pro versions 4.0.1 and below contain a SQL injection vulnerability (CVSS 8.5) allowing authenticated users to extract the entire WordPress database, including stored credentials and sensitive organizational data. No public exploit identified at time of analysis, but the absence of a vendor patch combined with high severity creates immediate risk of data breach and credential compromise for any organization running this plugin.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict subscriber-level user access through WordPress capability restrictions or disable the plugin if not business-critical; implement database backup procedures with secured offline storage; deploy database access monitoring and alerting for SQL injection attempts; configure Web Application Firewall (WAF) rules to block SQL injection payloads targeting database; isolate the WordPress database through network segmentation; require multi-factor authentication for all subscriber-level accounts; disable unused plugin features if functionality cannot be fully restricted.
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-64802
GHSA-w84f-pwww-634r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB