# CVE-2009-3703: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via multiple parameters in the WP-Forum plugin, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r8hf-cmf8-86j7

## What is CVE-2009-3703?

CVE-2009-3703 is a high-severity SQL injection vulnerability in n/a, published on 18 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the WP-Forum plugin before 2.4 for WordPress allow remote attackers to execute arbitrary SQL commands via (1) the search_max parameter in a search action to the default URI, related to wpf.class.php; (2) the forum parameter to an unspecified component, related to wpf.class.php; (3) the topic parameter in a viewforum action to the default URI, related to the remove_topic function in wpf.class.php; or the id parameter in a (4) editpost or (5) viewtopic action to the default URI, related to wpf-post.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2009-3703?

It affects 1 product.


Products: Fahlstad Wp-Forum.

## How do I fix CVE-2009-3703?

No fix has been published for CVE-2009-3703 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-3703 being exploited?

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

Public exploit code:

- WordPress Plugin WP-Forum 2.3 - SQL Injection / Blind SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3703 and fix it if it is affected.

What it is: CVE-2009-3703 is a high-severity SQL injection vulnerability in n/a, published on 18 Dec 2009. 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-2009-3703 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-2009-3703/ (Markdown: https://insights.sbomify.com/CVE-2009-3703/index.md)
```

## Sources

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

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