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

> Attackers can execute arbitrary code by uploading a crafted PHP file to the music management system's playlist save endpoint.

- **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:** 21 Aug 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-f8mh-6mf7-mh58

## What is CVE-2024-42778?

CVE-2024-42778 is a high-severity vulnerability in n/a, published on 21 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Unrestricted file upload vulnerability was found in "/music/ajax.php?action=save_playlist" in Kashipara Music Management System v1.0. This allows attackers to execute arbitrary code via uploading a crafted PHP file.

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

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

It affects 1 product.


Products: Lopalopa Music Management System.

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

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

## Is CVE-2024-42778 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-42797](https://insights.sbomify.com/CVE-2024-42797/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-42777](https://insights.sbomify.com/CVE-2024-42777/): File upload in n/a (critical 9.8)
- [CVE-2024-42781](https://insights.sbomify.com/CVE-2024-42781/): SQL injection in n/a (critical 9.8)
- [CVE-2024-42784](https://insights.sbomify.com/CVE-2024-42784/): SQL injection in n/a (critical 9.8)
- [CVE-2024-42791](https://insights.sbomify.com/CVE-2024-42791/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42778 is a high-severity vulnerability in n/a, published on 21 Aug 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-42778 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-42778/ (Markdown: https://insights.sbomify.com/CVE-2024-42778/index.md)
```

## Sources

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

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