# CVE-2021-34257: Unrestricted Upload of File with Dangerous Type in WPanel 4

> Attackers can execute arbitrary code by uploading malicious PHP files to various image upload fields in WPanel.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 31 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vhgr-gfx3-fg37

## What is CVE-2021-34257?

CVE-2021-34257 is a high-severity vulnerability in n/a, published on 31 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple Remote Code Execution (RCE) vulnerabilities exist in WPanel 4 4.3.1 and below via a malicious PHP file upload to (1) Dashboard's Avatar image, (2) Posts Folder image, (3) Pages Folder image and (4) Gallery Folder image.

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

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

2 open source packages ship an affected version, including wpanel/wpanel4-cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wpanel/wpanel4-cms` | Packagist | All versions to 4.3.1 | None |
| `wpanel/wpanel4-cms` | Packagist | All versions to 4.3.1 | None |

Products: Wpanel Cms Project Wpanel Cms.

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

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

## Is CVE-2021-34257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-34257 is a high-severity vulnerability in n/a, published on 31 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34257 in the wild and no public exploit code.

Affected packages and fixed versions:
- wpanel/wpanel4-cms (Packagist): affected all versions up to 4.3.1; no fix listed
- wpanel/wpanel4-cms (Packagist): affected all versions up to 4.3.1; no fix listed

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-34257/ (Markdown: https://insights.sbomify.com/CVE-2021-34257/index.md)
```

## Sources

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

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