# CVE-2008-4080: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Stash web application when magic_quotes_gpc is disabled, potentially compromising data integrity and confidentiality.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/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:** 15 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2020-15311, GHSA-mq5f-vwpq-7wpj

## What is CVE-2008-4080?

CVE-2008-4080 is a medium-severity SQL injection vulnerability in n/a, published on 15 Sep 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in Stash 1.0.3, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the (1) username parameter to admin/library/authenticate.php and the (2) download parameter to downloadmp3.php.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2008-4080?

It affects 1 product.


Products: Stash Stash.

## How do I fix CVE-2008-4080?

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

## Is CVE-2008-4080 being exploited?

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

Public exploit code:

- Stash 1.0.3 - Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-4590](https://insights.sbomify.com/CVE-2008-4590/): SQL injection in n/a (high 7.5)
- [CVE-2008-4081](https://insights.sbomify.com/CVE-2008-4081/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-4080 and fix it if it is affected.

What it is: CVE-2008-4080 is a medium-severity SQL injection vulnerability in n/a, published on 15 Sep 2008. 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-2008-4080 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-2008-4080/ (Markdown: https://insights.sbomify.com/CVE-2008-4080/index.md)
```

## Sources

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

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