# CVE-2024-5084: Hash Form – Drag & Drop Form Builder <= 1.1.0 - Unauthenticated Arbitrary File Upload to Remote Code Execution

> 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:** 23 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rgr9-6xwp-v98f

## What is CVE-2024-5084?

CVE-2024-5084 is a critical vulnerability in hashthemes Hash Form – Drag & Drop Form Builder, published on 23 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Hash Form – Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'file_upload_action' function in all versions up to, and including, 1.1.0. 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-2024-5084?

It affects 1 product.


Products: Hashthemes Hash Form.

## How do I fix CVE-2024-5084?

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

## Is CVE-2024-5084 being exploited?

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

Public exploit code:

- Hash Form – Drag & Drop Form Builder <= 1.1.0 - Unauthenticated Arbitrary File Upload to Remote Code Execution (github_poc): https://github.com/Chocapikk/CVE-2024-5084
- https://github.com/RedTeamBlueTeam/CVE-2024-5084-Red-Team (github_poc): https://github.com/RedTeamBlueTeam/CVE-2024-5084-Red-Team
- WordPress Hash Form Plugin RCE (metasploit)
- WordPress Hash Form – Drag & Drop Form Builder <= 1.1.0 - Unauthenticated Arbitrary File Upload to Remote Code Execution (github_poc): https://github.com/KTN1990/CVE-2024-5084
- https://github.com/NanoWraith/CVE-2024-5084 (github_poc): https://github.com/NanoWraith/CVE-2024-5084
- PoC Exploit for CVE-2024-5084 (github_poc): https://github.com/WOOOOONG/CVE-2024-5084

## Other vulnerabilities in hashthemes Hash Form – Drag & Drop Form Builder

- [CVE-2024-5085](https://insights.sbomify.com/CVE-2024-5085/): Hash Form – Drag & Drop Form Builder <= 1.1.0 - Unauthenticated PHP Object Injection (high 8.1)
- [CVE-2024-9417](https://insights.sbomify.com/CVE-2024-9417/): Hash Form - Drag & Drop Form Builder <= 1.1.9 - Unauthenticated Limited File Upload (medium 6.1)
- [CVE-2024-12201](https://insights.sbomify.com/CVE-2024-12201/): Hash Form <= 1.2.1 - Missing Authorization to Authenticated (Contributor+) Form Style Creation (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5084 and fix it if it is affected.

What it is: CVE-2024-5084 is a critical vulnerability in hashthemes Hash Form – Drag & Drop Form Builder, published on 23 May 2024. 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-2024-5084 exists.

Affected product: hashthemes Hash Form – Drag & Drop 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-2024-5084/ (Markdown: https://insights.sbomify.com/CVE-2024-5084/index.md)
```

## Sources

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

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