# CVE-2024-30500: WordPress CubeWP plugin <= 1.1.12 - Arbitrary File Upload vulnerability

> Attackers can upload malicious files to execute arbitrary code on WordPress sites using the CubeWP plugin.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-5wqc-p6hx-3xmx

## What is CVE-2024-30500?

CVE-2024-30500 is a critical vulnerability in CubeWP – All-in-One Dynamic Content Framework, published on 29 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in CubeWP CubeWP – All-in-One Dynamic Content Framework.This issue affects CubeWP – All-in-One Dynamic Content Framework: from n/a through 1.1.12.

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

## Which versions are affected by CVE-2024-30500?

It affects 1 product.


Products: Cubewp Cubewp.

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

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

## Is CVE-2024-30500 being exploited?

There is no known exploitation of CVE-2024-30500 in the wild and no public exploit code.

## Other vulnerabilities in CubeWP – All-in-One Dynamic Content Framework

- [CVE-2025-4315](https://insights.sbomify.com/CVE-2025-4315/): CubeWP – All-in-One Dynamic Content Framework <= 1.1.23 - Authenticated (Subscriber+) Privilege Escalation (high 8.8)
- [CVE-2024-48039](https://insights.sbomify.com/CVE-2024-48039/): WordPress CubeWP Framework plugin <= 1.1.15 - Broken Access Control vulnerability (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-30500 is a critical vulnerability in CubeWP – All-in-One Dynamic Content Framework, published on 29 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-30500 in the wild and no public exploit code.

Affected product: CubeWP – All-in-One Dynamic Content Framework. 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-30500/ (Markdown: https://insights.sbomify.com/CVE-2024-30500/index.md)
```

## Sources

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

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