# CVE-2024-34411: WordPress canvasio3D Light plugin <= 2.5.0 - Arbitrary File Upload vulnerability

> Attackers can upload malicious files to the canvasio3D Light WordPress plugin, potentially leading to remote code execution.

- **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:** 13 May 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-prmm-jjm7-hjjw

## What is CVE-2024-34411?

CVE-2024-34411 is a critical vulnerability in Thomas Scholl canvasio3D Light, published on 13 May 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 Thomas Scholl canvasio3D Light.This issue affects canvasio3D Light: from n/a through 2.5.0.

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

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


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

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

## Is CVE-2024-34411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34411 is a critical vulnerability in Thomas Scholl canvasio3D Light, published on 13 May 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-34411 in the wild and no public exploit code.

Affected product: Thomas Scholl canvasio3D Light. 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-34411/ (Markdown: https://insights.sbomify.com/CVE-2024-34411/index.md)
```

## Sources

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

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