CVE-2019-9568 json
The "Forminator Contact Form, Poll & Quiz Builder" plugin before 1.6 for WordPress has SQL Injection via the wp-admin/admin.php?page=formin…
published 7y ago modified 4mo ago also EUVD-2019-18939
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The "Forminator Contact Form, Poll & Quiz Builder" plugin before 1.6 for WordPress has SQL Injection via the wp-admin/admin.php?page=forminator-entries entry[] parameter if the attacker has the delete permission.
Patch / fix
- incsub forminator 1.6
Is CVE-2019-9568 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
1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- lists.openwall.net https://lists.openwall.net/full-disclosure/2019/02/05/4 referenced PoC, tagged "exploit" by a source, unverified
- security-consulting.icu https://security-consulting.icu/blog/2019/02/wordpress-forminator-persistent-xss-blind-sql-injection/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
lists.openwall.net
/full-disclosure/2019/02/05/4
exploit, third-party-advisory
-
security-consulting.icu
/blog/2019/02/wordpress-forminator-persistent-xss-blind-sql-injection/
exploit, third-party-advisory
-
wordpress.org
/plugins/forminator/#developers
release-notes, vendor-advisory
-
wpvulndb.com
/vulnerabilities/9215
third-party-advisory
Sources
- CVE List CVE-2019-9568
- NVD CVE-2019-9568
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.