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

> Authenticated users can execute arbitrary SQL commands in RunCMS forum module via pid or topic_id parameters, allowing data access or modification.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6pj7-7hg8-7vr5

## What is CVE-2009-3804?

CVE-2009-3804 is a medium-severity SQL injection vulnerability in n/a, published on 27 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in modules/forum/post.php in RunCMS 2M1 allow remote authenticated users to execute arbitrary SQL commands via (1) the pid parameter, which is not properly handled by the store function in modules/forum/class/class.forumposts.php, or (2) the topic_id parameter.

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

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

It affects 1 product.


Products: Runcms Runcms.

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

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

## Is CVE-2009-3804 being exploited?

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

Public exploit code:

- RunCMS - 'forum' SQL Injection (exploitdb)
- RunCMS 2m1 - 'store()' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5535](https://insights.sbomify.com/CVE-2007-5535/): Unspecified vulnerability in newbb_plus in RunCms 1.5.2 has unknown impact and attack vectors. (critical 10.0)
- [CVE-2007-2539](https://insights.sbomify.com/CVE-2007-2539/): Information disclosure in n/a (high 7.8)
- [CVE-2006-1793](https://insights.sbomify.com/CVE-2006-1793/): Path traversal in n/a (high 7.6)
- [CVE-2008-0224](https://insights.sbomify.com/CVE-2008-0224/): SQL injection in n/a (high 7.5)
- [CVE-2007-6544](https://insights.sbomify.com/CVE-2007-6544/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3804 is a medium-severity SQL injection vulnerability in n/a, published on 27 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3804 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-3804/ (Markdown: https://insights.sbomify.com/CVE-2009-3804/index.md)
```

## Sources

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

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