CVE-2019-15780 json
The formidable plugin before 4.02.01 for WordPress has unsafe deserialization.
published 7y ago modified 4mo ago also EUVD-2019-6704
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
The formidable plugin before 4.02.01 for WordPress has unsafe deserialization.
Patch / fix
- strategy11 formidable_form_builder 4.02.01
Is CVE-2019-15780 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.39% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/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-502 Deserialization of Untrusted Data
- Technology feeds
References
-
wordpress.org
/plugins/formidable/#developers
product, third-party-advisory
-
pentest.co.uk
/labs/advisory/cve-2019-15780/
third-party-advisory
-
raw.githubusercontent.com
/Strategy11/formidable-forms/master/changelog.txt
release-notes, third-party-advisory
-
wpvulndb.com
/vulnerabilities/9935
third-party-advisory
Sources
- CVE List CVE-2019-15780
- NVD CVE-2019-15780
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.