Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Author-level account on target WP ERP site
-
ExploitSend crafted request with SQL payload to plugin endpoint
-
ExecutionInjected query executes against WordPress DB
-
ImpactExtract sensitive HR/CRM and credential data
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 | Requires an authenticated WordPress session with at least Author-level privileges (PR:H) on a site running the WP ERP plugin version 1.17.9 or earlier; the vulnerable SQL-injection code path must be reachable by that role. No user interaction is needed (UI:N) and the attack is network-reachable (AV:N). Limiting factors: the Author privilege requirement excludes anonymous/subscriber attackers, so exposure is highest on multi-author sites, membership/community sites, or sites where Author accounts are granted to third parties; sites restricting Author-or-above accounts to fully trusted staff face materially lower risk. |
| Impact | This is a genuine but privilege-gated risk. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L, 7.6 HIGH) describes a network-reachable, low-complexity SQL injection that requires high privileges (PR:H) - consistent with Patchstack's 'Author SQL Injection' framing, meaning an authenticated user holding at least the WordPress Author role. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the supplied data, so all signals point to no known or automated exploitation to date; the elevated CVSS is driven by CWE-89's high confidentiality impact and the scope change (S:C) rather than by ease of access. No SSVC decision data was provided. Net: a real, patchable priority for sites that grant Author accounts to untrusted or semi-trusted users, but not an emergency mass-exploitation scenario - the PR:H requirement substantially narrows the attacker population versus an unauthenticated flaw. |
| Exploit ScenarioDerived | An attacker who already holds (or has phished/registered into) a WordPress Author-level account on a site running WP ERP <= 1.17.9 sends a crafted request to a vulnerable plugin endpoint, injecting SQL that the backend executes against the WordPress database. This lets them read sensitive data such as password hashes, HR/CRM records, and secrets stored by the ERP suite. No public exploit code was identified at time of analysis, and no user interaction is required beyond the attacker's own authenticated session. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Authenticated SQL injection in the weDevs WP ERP plugin for WordPress, affecting all releases up to and including 1.17.9, allows an attacker with Author-level or higher WordPress privileges to inject arbitrary SQL and read data from the site's database. The vulnerability is network-reachable and requires no user interaction, and because the CVSS scope is marked as changed (S:C) with high confidentiality impact (C:H), a successful injection can reach data beyond the plugin's own tables, including other plugins' and core WordPress content. Exploitation is privilege-gated by the PR:H rating, so exposure concentrates on multi-author, membership or community sites where Author accounts are handed to third parties; there is no public exploit identified at time of analysis and no confirmed vendor patch version in the available intelligence, making this a genuine but privilege-gated risk.
RemediationAI
No vendor-released patch version is identified in the available intelligence, so the first action is to consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/erp/vulnerability/wordpress-wp-erp-plugin-1-17-9-sql-injection-vulnerability and the weDevs WP ERP release notes to confirm whether a fixed release newer than 1.17.9 has shipped, then upgrade to that exact version once confirmed; monitoring the plugin's update channel is required because the fixed version is not yet pinned down. In the interim, apply compensating controls that directly target the PR:H gate: audit every Author-level and higher account, downgrade or remove any that are not strictly needed, and refrain from granting Author credentials to third parties, since that single control eliminates the practical attack surface; note the operational trade-off that reducing author roles may disrupt publishing workflows. Additional containment includes deploying a WAF rule set that inspects WP ERP request parameters for SQL metacharacters and union/comment patterns, accepting that aggressive signatures can break legitimate plugin functionality and should be run in detection mode first; restricting or blocking HTTP access to the plugin's administrative and AJAX entry points so that only trusted roles and source addresses can reach them, which may break legitimate ERP features for remote or low-privilege users; and deactivating the WP ERP plugin entirely on sites that do not depend on it, which removes the exposure but forfeits its ERP functionality. Finally, enable database query logging and monitor for anomalous SELECT activity from Author sessions, and rotate credentials plus review wp_users and plugin tables for evidence of exfiltration if the vulnerable version was exposed to untrusted authors.
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
The issue is a CWE-89 improper neutralization of special elements used in an SQL command (SQL injection) in the WordPress plugin WP ERP, published by weDevs and tracked under CPE cpe:2.3:a:wedevs:wp_erp:*:*:*:*:*:*:*:*, which denotes all versions up to and including 1.17.9. Like most WordPress plugins, WP ERP is written in PHP and performs database operations through the WordPress $wpdb abstraction; an SQLi of this class arises when a request parameter or field reaching a query is concatenated or interpolated into a statement without parameterized placeholders or adequate escaping. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L indicates the vulnerable code path is reachable over the network with low attack complexity, requires authenticated access at a privileged level (PR:H), needs no victim interaction (UI:N), and carries a scope change that reflects the plugin's queries executing against the shared WordPress database rather than an isolated component. The high confidentiality impact with no integrity impact is consistent with a read-oriented injection (for example a UNION- or subquery-based extraction), while the low availability impact suggests only marginal query or resource disruption. The scope change is significant because the same database holds core tables such as wp_users with password hashes, as well as data belonging to every other installed plugin.
Know when Wp Erp 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:H/UI:N/S:C/C:H/I:N/A:L
Network SQLi requiring Author role gives AV:N/AC:L/PR:H/UI:N; DB access beyond plugin bounds is S:C with C:H, no integrity impact and only minor availability, matching the vendor vector.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Author SQL Injection in WP ERP <= 1.17.9 versions.
Executive ViewAI
The weDevs WP ERP plugin for WordPress, versions up to and including 1.17.9, contains an authenticated SQL injection that allows users with Author-level or higher privileges to read data from the site’s database, potentially exposing content beyond the plugin’s own tables. Organizations running multi-author, membership, or community WordPress sites are most exposed because they commonly grant Author accounts to external contributors. Leadership should care because no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, meaning sensitive data could be read by a trusted-but-lower-privileged user while remediation options remain limited.
No vendor-released patch identified at time of analysis; interim mitigations include restricting Author-level and higher WordPress accounts to trusted users, disabling or removing the WP ERP plugin if not essential, enforcing least privilege, deploying WAF or virtual patching rules for SQL injection, monitoring database access logs, segmenting database privileges, and rotating database credentials.
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.
The ERP WordPress plugin before 1.12.4 does not properly sanitise and escape the `type` parameter in the `erp/v1/account
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
The ERP WordPress plugin before 1.12.4 does not sanitise and escape the employee_name parameter before outputting it bac
The WP ERP plugin for WordPress is vulnerable to SQL Injection via the ‘vendor_id’ and 'status' parameter in all version
SQL injection vulnerability in the weDevs WP ERP WordPress plugin affecting all versions up to and including 1.16.10, al
The WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs WP ERP | Co
The WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is
The WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is
The WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is
The WP ERP | Complete HR solution with recruitment & job listings | WooCommerce CRM & Accounting plugin for WordPress is
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs WP ERP erp
EUVD-2026-89859
GHSA-m8hr-j4rq-m427
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB