weDevs WP ERP privilege escalation in role assignment
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.0
- Who is exposed
- Specific setups only
Summary
Privilege escalation flaw in the WP ERP plugin from weDevs for WordPress, caused by incorrect privilege assignment. An attacker reaches it remotely with a low-privilege account and can gain higher privileges than they should have.
Written by a model
Original description
Incorrect Privilege Assignment vulnerability in weDevs WP ERP erp allows Privilege Escalation.This issue affects WP ERP: from n/a through 1.17.11.
Who should check
Sites running the WordPress WP ERP plugin version 1.17.11 or earlier, from weDevs
“WordPress WP ERP Plugin <= 1.17.11 is vulnerable”
What to do
Check whether your setup matches what the bug needs.
WP ERP plugin version 1.17.11 or earlierUpgrade to a fixed version: 2.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129036 (WordPress WP ERP plugin <= 1.17.11 - Privilege Escalation vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129036 (entry last updated 2026-11-20):
Affected:
- weDevs WP ERP: fixed in 2.0.0
Fixed versions: 2.0.0.
Conditions (all must be true for the bug to be hit):
- WP ERP plugin version 1.17.11 or earlier (source: https://patchstack.com/database/wordpress/plugin/erp/vulnerability/wordpress-wp-erp-plugin-1-17-11-privilege-escalation-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129036 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129036 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/erp/vulnerability/wordpress-wp-erp-plugin-1-17-11-privilege-escalation-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129036
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129036"}.Affected versions
- erpfixed in 2.0.0 · through 1.17.11
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 7.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129036 |
| Record | NVD · CVE-2026-129036 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/erp/vulnerability/wordpress-wp-erp-plugin-1-17-11-privilege-escalation-vulnerability?_s_id=cve |
Questions about CVE-2026-129036
Is CVE-2026-129036 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A low-privilege user of the WP ERP plugin can gain admin rights and then full control of the WordPress site. The bug is a privilege escalation flaw in the plugin.
Source: patchstack.com
Which versions are affected by CVE-2026-129036?
erp: through 1.17.11 (fixed in 2.0.0).
Source: cve.now feed data
Am I affected, and how do I check?
The flaw affects WP ERP plugin version 1.17.11 and earlier. To check, look at the plugin version listed on the WordPress Plugins screen or in the plugin's header in the wp-content/plugins/ folder.
Source: patchstack.com
How do I fix CVE-2026-129036?
Upgrade to a fixed version: 2.0.0. The vendor's advisory also recommends 2.0.0 or later or later.
Source: cve.now feed data, patchstack.com
Related
- CVE-2026-31917WordPress WP ERP plugin <= 1.16.10 - SQL Injection vulnerability
- CVE-2026-96346WordPress WP ERP plugin <= 1.17.9 - SQL Injection vulnerability
- CVE-2024-21747WordPress WP ERP Plugin <= 1.12.8 is vulnerable to SQL Injection
- CVE-2026-4834WP ERP Pro <= 1.5.1 - Unauthenticated SQL Injection via 'search_key' Parameter
- CVE-2026-96343WordPress WP ERP plugin <= 1.17.9 - PHP Object Injection vulnerability
- CVE-2024-47640WordPress WP ERP plugin <= 1.13.2 - Reflected Cross Site Scripting (XSS) vulnerability
No corrections so far. Something wrong on this page? Report an error.