# CVE-2008-5113: Cross-site request forgery in n/a

> Remote attackers can perform persistent CSRF attacks to delete user accounts or cause denial of service by exploiting cookie injection vulnerabilities.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5113, GHSA-m5gr-m2fc-vhr6

## What is CVE-2008-5113?

CVE-2008-5113 is a medium-severity vulnerability in Wordpress Wordpress, published on 17 Nov 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

WordPress 2.6.3 relies on the REQUEST superglobal array in certain dangerous situations, which makes it easier for remote attackers to conduct delayed and persistent cross-site request forgery (CSRF) attacks via crafted cookies, as demonstrated by attacks that (1) delete user accounts or (2) cause a denial of service (loss of application access).  NOTE: this issue relies on the presence of an independent vulnerability that allows cookie injection.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2008-5113?

It affects 1 product.


Products: Wordpress Wordpress.

## How do I fix CVE-2008-5113?

Upgrade to a fixed version.

## Is CVE-2008-5113 being exploited?

There is no known exploitation of CVE-2008-5113 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-2008-5113 and fix it if it is affected.

What it is: CVE-2008-5113 is a medium-severity vulnerability in Wordpress Wordpress, published on 17 Nov 2008. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-5113 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-2008-5113/ (Markdown: https://insights.sbomify.com/CVE-2008-5113/index.md)
```

## Sources

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

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