# CVE-2013-0235: Server-side request forgery in n/a

> Remote attackers can exploit WordPress XMLRPC pingbacks to perform Server-Side Request Forgery, enabling intranet access and port scanning.

- **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:** 8 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-0235, GHSA-h9g4-hjrv-3hqw

## What is CVE-2013-0235?

CVE-2013-0235 is a medium-severity server-side request forgery vulnerability in Wordpress Wordpress, published on 8 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The XMLRPC API in WordPress before 3.5.1 allows remote attackers to send HTTP requests to intranet servers, and conduct port-scanning attacks, by specifying a crafted source URL for a pingback, related to a Server-Side Request Forgery (SSRF) issue.

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2013-0235 being exploited?

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

Public exploit code:

- Wordpress Pingback Locator (metasploit)

## 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-0235 and fix it if it is affected.

What it is: CVE-2013-0235 is a medium-severity server-side request forgery vulnerability in Wordpress Wordpress, published on 8 Jul 2013. 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-2013-0235 exists.

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

## Sources

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

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