CVE-2023-4596 in the critical feed json
Forminator <= 1.24.6 - Unauthenticated Arbitrary File Upload
published 3y ago modified 5mo ago also EUVD-2023-54449
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.3%
- EPSS 14.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
The Forminator plugin for WordPress is vulnerable to arbitrary file uploads due to file type validation occurring after a file has been uploaded to the server in the upload_post_image() function in versions up to, and including, 1.24.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Patch / fix
Is CVE-2023-4596 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
14.32% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-22).
Exploits and checks
- exploit-db.com https://www.exploit-db.com/exploits/51664 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2954409/forminator/trunk/library/fields/postdata.php
patch
-
exploit-db.com
/exploits/51664
exploit, third-party-advisory, vdb-entry
-
wordfence.com
/threat-intel/vulnerabilities/id/9cd87da6-1f4c-4a15-8ebb-6e0f8ef72513?source=cve
third-party-advisory
Sources
- CVE List CVE-2023-4596
- NVD CVE-2023-4596
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.