# CVE-2006-5031: CakePHP directory traversal vulnerability allows remote attackers to read arbitrary files

> Remote attackers can read arbitrary files via directory traversal in the vendors.php script, exposing sensitive data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 27 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-5031, GHSA-rw73-xmpv-j5x2

## What is CVE-2006-5031?

CVE-2006-5031 is a medium-severity path traversal vulnerability in n/a, published on 27 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in app/webroot/js/vendors.php in Cake Software Foundation CakePHP before 1.1.8.3544 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter, followed by a filename ending with "%00" and a .js filename.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including cakephp/cakephp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cakephp/cakephp` | Packagist | From 1.0.1.2708 | 1.1.8.3544 |
| `cakephp/cakephp` | Packagist | From 1.0.1.2708 | 1.1.8.3544 |

Products: Cakephp Cakephp.

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

Upgrade cakephp/cakephp to 1.1.8.3544 or later.

## Is CVE-2006-5031 being exploited?

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

Public exploit code:

- CakePHP 1.1.7.3363 - 'Vendors.php' Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-22727](https://insights.sbomify.com/CVE-2023-22727/): Database Query::offset() and limit() vulnerable to SQL injection in cakephp (critical 9.8)
- [CVE-2020-35239](https://insights.sbomify.com/CVE-2020-35239/): CakePHP allows method override parameters to bypass CSRF checks (high 8.8)
- [CVE-2015-8379](https://insights.sbomify.com/CVE-2015-8379/): CakePHP might allow remote attackers to bypass CSRF protection mechanism via the _method parameter (high 8.8)
- [CVE-2019-11458](https://insights.sbomify.com/CVE-2019-11458/): Unsafe deserialization in SmtpTransport in CakePHP (high 7.5)
- [CVE-2016-4793](https://insights.sbomify.com/CVE-2016-4793/): CakePHP allows remote attackers to spoof their IP (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-5031 is a medium-severity path traversal vulnerability in n/a, published on 27 Sep 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-5031 exists.

Affected packages and fixed versions:
- cakephp/cakephp (Packagist): affected from 1.0.1.2708; fixed in 1.1.8.3544
- cakephp/cakephp (Packagist): affected from 1.0.1.2708; fixed in 1.1.8.3544

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

## Sources

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

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