# CVE-2025-52921: File upload in InnoShop

> Authenticated attackers can achieve remote code execution by bypassing frontend restrictions to rename uploaded files to .php extensions.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **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:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-xp47-r464-469h

## What is CVE-2025-52921?

CVE-2025-52921 is a critical vulnerability in InnoShop, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Innoshop through 0.4.1, an authenticated attacker could exploit the File Manager functions in the admin panel to achieve code execution on the server, by uploading a crafted file and then renaming it to have a .php extension by using the Rename Function. This bypasses the initial check that uploaded files are image files. The application relies on frontend checks to restrict the administrator from changing the extension of uploaded files to .php. This restriction is easily bypassed with any proxy tool (e.g., BurpSuite). Once the attacker renames the file, and gives it the .php extension, a GET request can be used to trigger the execution of code on the server.

Weakness: CWE-420 (Unprotected Alternate Channel)

## Which versions are affected by CVE-2025-52921?


## How do I fix CVE-2025-52921?

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

## Is CVE-2025-52921 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52921 and fix it if it is affected.

What it is: CVE-2025-52921 is a critical vulnerability in InnoShop, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52921 in the wild and no public exploit code.

Affected product: InnoShop. 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-2025-52921/ (Markdown: https://insights.sbomify.com/CVE-2025-52921/index.md)
```

## Sources

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

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