# CVE-2024-25802: File upload in n/a

> Attackers can upload malicious files via the Add Media function in SKINsoft S-Museum, potentially leading to remote code execution.

- **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:** 22 Feb 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-gp72-c58g-57q3

## What is CVE-2024-25802?

CVE-2024-25802 is a critical vulnerability in n/a, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SKINsoft S-Museum 7.02.3 allows Unrestricted File Upload via the Add Media function. Unlike in CVE-2024-25801, the attack payload is the file content.

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

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

It affects 1 product.


Products: Skinsoft S-Museum.

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

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

## Is CVE-2024-25802 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-25801](https://insights.sbomify.com/CVE-2024-25801/): Cross-site scripting in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25802 is a critical vulnerability in n/a, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25802 in the wild and no public exploit code.

Affected product: n/a. 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-25802/ (Markdown: https://insights.sbomify.com/CVE-2024-25802/index.md)
```

## Sources

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

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