# CVE-2013-2203: Information disclosure in n/a

> Remote attackers can obtain sensitive absolute path information via invalid upload requests when write access is restricted.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2203, GHSA-p2ph-58w4-xr4f

## What is CVE-2013-2203?

CVE-2013-2203 is a medium-severity vulnerability in Wordpress Wordpress, published on 8 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WordPress before 3.5.2, when the uploads directory forbids write access, allows remote attackers to obtain sensitive information via an invalid upload request, which reveals the absolute path in an XMLHttpRequest error message.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2203?

It affects 1 product.


Products: Wordpress Wordpress.

## How do I fix CVE-2013-2203?

Upgrade to a fixed version.

## Is CVE-2013-2203 being exploited?

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

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2203 and fix it if it is affected.

What it is: CVE-2013-2203 is a medium-severity vulnerability in Wordpress Wordpress, published on 8 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2203 in the wild and no public exploit code.

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

## Sources

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

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