# CVE-2012-0057: File upload in n/a

> Remote attackers can create arbitrary files on the server by exploiting improper libxslt security settings in PHP via crafted XSLT stylesheets.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 2 Feb 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g9fj-7hhm-6873

## What is CVE-2012-0057?

CVE-2012-0057 is a medium-severity vulnerability in Php Php, published on 2 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP before 5.3.9 has improper libxslt security settings, which allows remote attackers to create arbitrary files via a crafted XSLT stylesheet that uses the libxslt output extension.

Weakness: CWE-264

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2012-0057 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0057 is a medium-severity vulnerability in Php Php, published on 2 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0057 in the wild and no public exploit code.

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

## Sources

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

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