CVE-2019-15111 json
The wp-front-end-profile plugin before 0.2.2 for WordPress has a privilege escalation issue.
published 7y ago modified 4mo ago also EUVD-2019-6182
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
The wp-front-end-profile plugin before 0.2.2 for WordPress has a privilege escalation issue.
Patch / fix
- wp_front_end_profile_project wp_front_end_profile 0.2.2
Is CVE-2019-15111 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 FencerExploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
wordpress.org
/plugins/wp-front-end-profile/#developers
release-notes
Sources
- CVE List CVE-2019-15111
- NVD CVE-2019-15111
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.