CVE-2019-15871 json
The LoginPress plugin before 1.1.4 for WordPress has no capability check for updates to settings.
published 7y ago modified 4mo ago also EUVD-2019-6782
- cvss
- 4.3
- version 3.0, NVD
- 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 LoginPress plugin before 1.1.4 for WordPress has no capability check for updates to settings.
Patch / fix
- wpbrigade loginpress 1.1.4
Is CVE-2019-15871 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
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- webarxsecurity.com https://www.webarxsecurity.com/loginpress-plugin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
webarxsecurity.com
/loginpress-plugin/
exploit, third-party-advisory
-
wordpress.org
/plugins/loginpress/#developers
release-notes, third-party-advisory
Sources
- CVE List CVE-2019-15871
- NVD CVE-2019-15871
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.