CVE-2023-3636 json
WP Project Manager <= 2.6.4 - Arbitrary Usermeta Update to Authenticated (Subscriber+) Privilege Escalation
published 3y ago modified 5mo ago also EUVD-2023-44281
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
The WP Project Manager plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 2.6.4 due to insufficient restriction on the 'save_users_map_name' function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to modify their user role by supplying the 'usernames' parameter.
Patch / fix
- wedevs wp_project_manager 2.6.5
Is CVE-2023-3636 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.86% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-22).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- wedevs Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2942291/wedevs-project-manager#file1792
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/6a5e4708-db3e-483c-852f-1a487825cf92?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/wedevs-project-manager/tags/2.6.3/src/User/Controllers/User_Controller.php#L158
product
Sources
- CVE List CVE-2023-3636
- NVD CVE-2023-3636
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.