# CVE-2012-4399: CakePHPallows remote attackers to read arbitrary files via XML data containing external entity references

> Remote attackers can read arbitrary files via XML external entity injection in the CakePHP Xml class.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 9 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5964-pq8r-4q62

## What is CVE-2012-4399?

CVE-2012-4399 is a high-severity vulnerability in n/a, published on 9 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Xml class in CakePHP 2.1.x before 2.1.5 and 2.2.x before 2.2.1 allows remote attackers to read arbitrary files via XML data containing external entity references, aka an XML external entity (XXE) injection attack.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2012-4399?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cakephp/cakephp` | Packagist | From 2.1.0-alpha | 2.1.5 |
| `cakephp/cakephp` | Packagist | From 2.1.0-alpha | 2.1.5 |
| `cakephp/cakephp` | Packagist | From 2.2.0-beta | 2.2.1 |
| `cakephp/cakephp` | Packagist | From 2.2.0-beta | 2.2.1 |

Products: Cakefoundation Cakephp.

## How do I fix CVE-2012-4399?

Upgrade cakephp/cakephp to a fixed version for your release line: 2.1.5 or 2.2.1.

## Is CVE-2012-4399 being exploited?

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

Public exploit code:

- CakePHP 2.x < 2.2.0-RC2 - XML External Entity Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-4335](https://insights.sbomify.com/CVE-2010-4335/): CakePHP allows remote attackers to modify internal Cake cache and execute arbitrary code (high 7.5)
- [CVE-2020-15400](https://insights.sbomify.com/CVE-2020-15400/): Cross-Site Request Forgery in CakePHP (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4399 and fix it if it is affected.

What it is: CVE-2012-4399 is a high-severity vulnerability in n/a, published on 9 Oct 2012. 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-2012-4399 exists.

Affected packages and fixed versions:
- cakephp/cakephp (Packagist): affected from 2.1.0-alpha; fixed in 2.1.5
- cakephp/cakephp (Packagist): affected from 2.1.0-alpha; fixed in 2.1.5
- cakephp/cakephp (Packagist): affected from 2.2.0-beta; fixed in 2.2.1
- cakephp/cakephp (Packagist): affected from 2.2.0-beta; fixed in 2.2.1

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

## Sources

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

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