# CVE-2006-0787: Other in n/a

> Remote attackers can inject arbitrary data into track files, causing disk exhaustion or facilitating other exploits via parameter manipulation.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m886-7hq8-rv56

## What is CVE-2006-0787?

CVE-2006-0787 is a medium-severity vulnerability in n/a, published on 19 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wimpy_trackplays.php in Plaino Wimpy MP3 Player, possibly 5.2 and earlier, allows remote attackers to insert arbitrary strings into trackme.txt via the (1) trackFile, (2) trackArtist, and (3) trackTitle parameters, which can result in providing false information about songs, occupying excessive disk space with very long parameter values, and storing executable code that might be invoked through a different vulnerability.  NOTE: since this issue, as described by the original researcher, is entirely dependent on the presence of another vulnerability, it could be argued that Wimpy cannot be responsible for how its data file is processed by applications outside of its control. Since this issue might only be useful as a facilitator manipulation in another vulnerability, perhaps it should not be included in CVE.

## Which versions are affected by CVE-2006-0787?

It affects 1 product.


Products: Plaino Wimpy Mp3.

## How do I fix CVE-2006-0787?

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

## Is CVE-2006-0787 being exploited?

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

Public exploit code:

- Wimpy MP3 Player 5 - Text File Overwrite (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0787 and fix it if it is affected.

What it is: CVE-2006-0787 is a medium-severity vulnerability in n/a, published on 19 Feb 2006. 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-2006-0787 exists.

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

## Sources

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

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