The pie-register plugin before 3.1.2 for WordPress has SQL injection, a different issue than CVE-2018-10969.

published 2019-08-27 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6609

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

Patch / fix

fixed in 1

genetechsolutions pie_register 3.1.2

Is CVE-2019-15659 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

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

Weakness

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

Technology feeds

WordPress rss critical rss

References

wordpress.org /plugins/pie-register/#developers
release-notes
wpvulndb.com /vulnerabilities/9835
third-party-advisory

Sources

CVE List CVE-2019-15659
NVD CVE-2019-15659

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.