The LoginPress plugin before 1.1.4 for WordPress has SQL injection via an import of settings.

published 2019-09-03 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6783

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.2%; EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits: 0; none known

Patch / fix

fixed in 1

wpbrigade loginpress 1.1.4

Is CVE-2019-15872 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 Fencer

Exploit prediction

2.21% chance of exploitation in the next 30 days, higher than 82% 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	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

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

Technology feeds

WordPress rss critical rss

References

webarxsecurity.com /loginpress-plugin/
exploit, third-party-advisory
wordpress.org /plugins/loginpress/#developers
release-notes, third-party-advisory

Sources

CVE List CVE-2019-15872
NVD CVE-2019-15872

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.