CVE-2021-34622 json
ProfilePress 3.0 - 3.1.3 - Authenticated Privilege Escalation
published 5y ago modified 4mo ago also EUVD-2021-21272
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.9%
- EPSS 4.9% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
A vulnerability in the user profile update component found in the ~/src/Classes/EditUserProfile.php file of the ProfilePress WordPress plugin made it possible for users to escalate their privileges to that of an administrator while editing their profile. This issue affects versions 3.0.0 - 3.1.3. .
Is CVE-2021-34622 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
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
4.93% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template WordPress ProfilePress <= 3.1.3 - Privilege Escalation nuclei detection template
- wordfence.com https://www.wordfence.com/blog/2021/06/easily-exploitable-critical-vulnerabilities-patched-in-profilepress-plugin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- ProfilePress ProfilePress
- properfraction profilepress
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
-
wordfence.com
/blog/2021/06/easily-exploitable-critical-vulnerabilities-patched-in-profilepress-plugin/
exploit, third-party-advisory
Sources
- CVE List CVE-2021-34622
- NVD CVE-2021-34622
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.