# CVE-2007-2714: Unspecified vulnerability in akismet.php in Matt Mullenweg Akismet before 2.0.2, a WordPress plugin, has unknown impact and attack vectors.


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 16 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2714, GHSA-4m39-5qw8-66hm

## What is CVE-2007-2714?

CVE-2007-2714 is a critical vulnerability in n/a, published on 16 May 2007. 

### Official description

Unspecified vulnerability in akismet.php in Matt Mullenweg Akismet before 2.0.2, a WordPress plugin, has unknown impact and attack vectors.

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

It affects 1 product.


Products: Matt Mullenweg Akismet.

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

Upgrade to a fixed version.

## Is CVE-2007-2714 being exploited?

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

Public exploit code:

- WordPress Plugin Akismet 2.1.3 - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2714 and fix it if it is affected.

What it is: CVE-2007-2714 is a critical vulnerability in n/a, published on 16 May 2007. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2714 exists.

Affected product: n/a. 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-2714/ (Markdown: https://insights.sbomify.com/CVE-2007-2714/index.md)
```

## Sources

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

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