# CVE-2007-1244: Cross-site request forgery in n/a

> Remote attackers can trick administrators into performing privileged actions via CSRF, potentially leading to account takeover or XSS.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1244, GHSA-pj8j-hmc8-6q85

## What is CVE-2007-1244?

CVE-2007-1244 is a medium-severity vulnerability in Wordpress Wordpress, published on 3 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the AdminPanel in WordPress 2.1.1 and earlier allows remote attackers to perform privileged actions as administrators, as demonstrated using the delete action in wp-admin/post.php.  NOTE: this issue can be leveraged to perform cross-site scripting (XSS) attacks and steal cookies via the post parameter.

## Which versions are affected by CVE-2007-1244?

It affects 1 product.


Products: Wordpress Wordpress.

## How do I fix CVE-2007-1244?

Upgrade to a fixed version.

## Is CVE-2007-1244 being exploited?

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

Public exploit code:

- WordPress Core 2.1.1 - 'post.php' Cross-Site Scripting (exploitdb)

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

What it is: CVE-2007-1244 is a medium-severity vulnerability in Wordpress Wordpress, published on 3 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1244 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-2007-1244/ (Markdown: https://insights.sbomify.com/CVE-2007-1244/index.md)
```

## Sources

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

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