# CVE-2006-0567: Path traversal in n/a

> Remote attackers can read files outside the web root via path traversal in the Xaraya module when the Archive Directory is blank.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7mqw-w76j-7p24

## What is CVE-2006-0567?

CVE-2006-0567 is a medium-severity path traversal vulnerability in n/a, published on 7 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in Files Xaraya module before 0.5.1, when the Archive Directory field on the Modify Config page is blank, allows remote attackers to access files outside of the web root via ".." (dot dot) sequences.

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

It affects 1 product.


Products: Curtis Farnham Files Xaraya Module.

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

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

## Is CVE-2006-0567 being exploited?

There is no known exploitation of CVE-2006-0567 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0567 is a medium-severity path traversal vulnerability in n/a, published on 7 Feb 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0567 in the wild and no public exploit code.

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

## Sources

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

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