# CVE-2012-3881: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via unspecified parameters in RTG and RTG2 web applications.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-chj4-9jvp-pjch

## What is CVE-2012-3881?

CVE-2012-3881 is a high-severity SQL injection vulnerability in n/a, published on 12 Jul 2012. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in RTG 0.7.4 and RTG2 0.9.2 allow remote attackers to execute arbitrary SQL commands via unspecified parameters to (1) 95.php, (2) view.php, or (3) rtg.php.

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

## Which versions are affected by CVE-2012-3881?

It affects 2 products.


Products: Adrian Chadd Rtg, Adrian Chadd Rtg2.

## How do I fix CVE-2012-3881?

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

## Is CVE-2012-3881 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3881 and fix it if it is affected.

What it is: CVE-2012-3881 is a high-severity SQL injection vulnerability in n/a, published on 12 Jul 2012. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3881 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-2012-3881/ (Markdown: https://insights.sbomify.com/CVE-2012-3881/index.md)
```

## Sources

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

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