# CVE-2023-4596: Forminator <= 1.24.6 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files to the server, potentially leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g9m5-p82f-mqgm

## What is CVE-2023-4596?

CVE-2023-4596 is a critical vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 30 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-4596?

It affects 1 product.


Products: Incsub Forminator.

## How do I fix CVE-2023-4596?

No fix has been published for CVE-2023-4596 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-4596 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4596 exists.

Public exploit code:

- PoC Script for CVE-2023-4596, unauthenticated Remote Command Execution through arbitrary file uploads. (github_poc): https://github.com/E1A/CVE-2023-4596
- CVE-2024-6387-checker is a tool or script designed to detect the security vulnerability known as CVE-2024-6387 OpenSSH. CVE-2024-6387 OpenSSH is an entry in the Common Vulnerabilities and Exposures (CVE) that documents security weaknesses discovered in certain software or systems. (github_poc): https://github.com/X-Projetion/CVE-2023-4596-OpenSSH-Multi-Checker
- CVE-2023-4596 Vulnerable Exploit and Checker Version (github_poc): https://github.com/X-Projetion/CVE-2023-4596-Vulnerable-Exploit-and-Checker-Version
- WordPress Plugin Forminator 1.24.6 - Arbitrary File Upload (nuclei): http/cves/2023/CVE-2023-4596.yaml

## Other vulnerabilities in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder

- [CVE-2025-6463](https://insights.sbomify.com/CVE-2025-6463/): Path traversal in Forminator Forms – Contact Form, Payment Form & Custom Form Builder (high 8.8)
- [CVE-2025-6464](https://insights.sbomify.com/CVE-2025-6464/): Deserialization in Forminator Forms – Contact Form, Payment Form & Custom Form Builder (high 7.5)
- [CVE-2024-7389](https://insights.sbomify.com/CVE-2024-7389/): Forminator <= 1.29.1 - HubSpot Developer API Key Sensitive Information Exposure (high 7.5)
- [CVE-2024-31077](https://insights.sbomify.com/CVE-2024-31077/): SQL injection in Forminator (high 7.2)
- [CVE-2024-1794](https://insights.sbomify.com/CVE-2024-1794/): Forminator <= 1.29.0 - Unauthenticated Stored Cross-Site Scripting via File Upload (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4596 and fix it if it is affected.

What it is: CVE-2023-4596 is a critical vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 30 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4596 exists.

Affected product: wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-4596/ (Markdown: https://insights.sbomify.com/CVE-2023-4596/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4596
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4596
- OSV: https://osv.dev/vulnerability/CVE-2023-4596

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-4596/
Summaries are generated and may contain mistakes; the official description above is the record.