# CVE-2018-25181: Musicco 2.0.0 Arbitrary Directory Download via Path Traversal

> Unauthenticated attackers can download arbitrary system directories via path traversal in the getAlbum endpoint, exposing sensitive data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-7x79-6w56-ww2p

## What is CVE-2018-25181?

CVE-2018-25181 is a high-severity path traversal vulnerability in Musicco, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Musicco 2.0.0 contains a path traversal vulnerability that allows unauthenticated attackers to download arbitrary directories by manipulating the parent parameter. Attackers can supply directory traversal sequences in the parent parameter of the getAlbum endpoint to access sensitive system directories and download them as ZIP files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-25181?


## How do I fix CVE-2018-25181?

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

## Is CVE-2018-25181 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25181 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25181 and fix it if it is affected.

What it is: CVE-2018-25181 is a high-severity path traversal vulnerability in Musicco, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25181 exists.

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

## Sources

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

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