# CVE-2005-1524: File upload in n/a

> Remote attackers can execute arbitrary PHP code in Cacti via a file inclusion vulnerability in the graph header script.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1524, GHSA-x9gq-h28h-fhwf

## What is CVE-2005-1524?

CVE-2005-1524 is a medium-severity vulnerability in n/a, published on 22 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP file inclusion vulnerability in top_graph_header.php in Cacti 0.8.6d and possibly earlier versions allows remote attackers to execute arbitrary PHP code via the config[library_path] parameter.

## Which versions are affected by CVE-2005-1524?

It affects 1 product.


Products: The Cacti Group Cacti.

## How do I fix CVE-2005-1524?

Upgrade to a fixed version.

## Is CVE-2005-1524 being exploited?

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

Public exploit code:

- RaXnet Cacti 0.5/0.6/0.8 - 'Top_Graph_Header.php' Remote File Inclusion (exploitdb)
- RaXnet Cacti 0.5/0.6.x/0.8.x - 'Graph_Image.php' Remote Command Execution Variant (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-2149](https://insights.sbomify.com/CVE-2005-2149/): SQL injection in n/a (critical 10.0)
- [CVE-2002-1478](https://insights.sbomify.com/CVE-2002-1478/): Command injection in n/a (critical 10.0)
- [CVE-2007-3112](https://insights.sbomify.com/CVE-2007-3112/): Denial of service in n/a (high 7.8)
- [CVE-2006-6799](https://insights.sbomify.com/CVE-2006-6799/): SQL injection in n/a (high 7.5)
- [CVE-2005-2148](https://insights.sbomify.com/CVE-2005-2148/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1524 and fix it if it is affected.

What it is: CVE-2005-1524 is a medium-severity vulnerability in n/a, published on 22 Jun 2005. 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-2005-1524 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-2005-1524/ (Markdown: https://insights.sbomify.com/CVE-2005-1524/index.md)
```

## Sources

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

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