# CVE-2010-4812: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable parameters in 6kbbs, potentially accessing or modifying database contents.

- **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:** 8 Jul 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rwvf-hg32-j97c

## What is CVE-2010-4812?

CVE-2010-4812 is a medium-severity SQL injection vulnerability in n/a, published on 8 Jul 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in 6kbbs 8.0 build 20100901 allow remote attackers to execute arbitrary SQL commands via the (1) tids[] parameter to ajaxadmin.php and the (2) msgids[] parameter to ajaxmember.php.

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

## Which versions are affected by CVE-2010-4812?

It affects 1 product.


Products: 6kbbs 6kbbs.

## How do I fix CVE-2010-4812?

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

## Is CVE-2010-4812 being exploited?

There is no known exploitation of CVE-2010-4812 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-9292](https://insights.sbomify.com/CVE-2015-9292/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2010-4811](https://insights.sbomify.com/CVE-2010-4811/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4812 and fix it if it is affected.

What it is: CVE-2010-4812 is a medium-severity SQL injection vulnerability in n/a, published on 8 Jul 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4812 in the wild and no public exploit code.

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-2010-4812/ (Markdown: https://insights.sbomify.com/CVE-2010-4812/index.md)
```

## Sources

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

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