# CVE-2005-0411: Path traversal in n/a

> Remote attackers can include arbitrary PHP files via directory traversal in the load parameter, potentially leading to code execution or data disclosure.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 16 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4rcx-jwpr-7mp7

## What is CVE-2005-0411?

CVE-2005-0411 is a high-severity path traversal vulnerability in n/a, published on 16 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php for CitrusDB 0.3.6 and earlier allows remote attackers and local users to include arbitrary PHP files via .. (dot dot) sequences in the load parameter.

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

It affects 1 product.


Products: Citrusdb Citrusdb.

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

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

## Is CVE-2005-0411 being exploited?

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

Public exploit code:

- CitrusDB 0.3.6 - Arbitrary Local PHP File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0408](https://insights.sbomify.com/CVE-2005-0408/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2005-0409](https://insights.sbomify.com/CVE-2005-0409/): Missing authorization in n/a (medium 6.4)
- [CVE-2005-0410](https://insights.sbomify.com/CVE-2005-0410/): SQL injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0411 is a high-severity path traversal vulnerability in n/a, published on 16 Feb 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-0411 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-0411/ (Markdown: https://insights.sbomify.com/CVE-2005-0411/index.md)
```

## Sources

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

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