# CVE-2021-24499: Workreap theme < 2.2.2 - Unauthenticated Upload Leading to Remote Code Execution

> Unauthenticated attackers can upload arbitrary files, including executable PHP scripts, leading to remote code execution on the server.

- **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:** 9 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r7ww-r6jj-2jrh

## What is CVE-2021-24499?

CVE-2021-24499 is a critical vulnerability in Unknown Workreap, published on 9 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Workreap WordPress theme before 2.2.2 AJAX actions workreap_award_temp_file_uploader and workreap_temp_file_uploader did not perform nonce checks, or validate that the request is from a valid user in any other way. The endpoints allowed for uploading arbitrary files to the uploads/workreap-temp directory. Uploaded files were neither sanitized nor validated, allowing an unauthenticated visitor to upload executable code such as php scripts.

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

## Which versions are affected by CVE-2021-24499?

It affects 1 product.


Products: Amentotech Workreap.

## How do I fix CVE-2021-24499?

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

## Is CVE-2021-24499 being exploited?

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

Public exploit code:

- Mass exploitation of CVE-2021-24499 unauthenticated upload leading to remote code execution in Workreap theme. (github_poc): https://github.com/j4k0m/CVE-2021-24499
- https://github.com/hh-hunter/cve-2021-24499 (github_poc): https://github.com/hh-hunter/cve-2021-24499
- WordPress Theme Workreap 2.2.2 - Unauthenticated Upload Leading to Remote Code Execution (exploitdb)
- https://github.com/jytmX/CVE-2021-24499 (github_poc): https://github.com/jytmX/CVE-2021-24499
- WordPress Theme Workreap 2.2.2 - Unauthenticated Upload Leading to Remote Code Execution (github_poc): https://github.com/jayhutajulu1/CVE-2021-24499
- WordPress Workreap - Remote Code Execution (nuclei): http/cves/2021/CVE-2021-24499.yaml

## Other vulnerabilities in Unknown Workreap

- [CVE-2025-4973](https://insights.sbomify.com/CVE-2025-4973/): Workreap <= 3.3.1 - Authentication Bypass via 'workreap_verify_user_account' (critical 9.8)
- [CVE-2024-13446](https://insights.sbomify.com/CVE-2024-13446/): Workreap <= 3.2.5 - Unauthenticated Privilege Escalation via Account Takeover (critical 9.8)
- [CVE-2025-5012](https://insights.sbomify.com/CVE-2025-5012/): Workreap <= 3.3.2 - Authenticated (Subscriber+) Arbitrary File Upload via 'workreap_temp_upload_to_media' (high 8.8)
- [CVE-2021-24500](https://insights.sbomify.com/CVE-2021-24500/): Workreap theme < 2.2.2 - Multiple CSRF + IDOR Vulnerabilities (high 8.1)
- [CVE-2021-24501](https://insights.sbomify.com/CVE-2021-24501/): Workreap theme < 2.2.2 - Missing Authorization Checks in Ajax Actions (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24499 and fix it if it is affected.

What it is: CVE-2021-24499 is a critical vulnerability in Unknown Workreap, published on 9 Aug 2021. 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-2021-24499 exists.

Affected product: Unknown Workreap. 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-2021-24499/ (Markdown: https://insights.sbomify.com/CVE-2021-24499/index.md)
```

## Sources

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

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