# CVE-2011-4460: SQL injection in n/a

> Authenticated privileged users can execute arbitrary SQL commands in RT, potentially compromising database integrity and confidentiality.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4460, GHSA-m7h5-crh5-vmfc

## What is CVE-2011-4460?

CVE-2011-4460 is a medium-severity SQL injection vulnerability in n/a, published on 4 Jun 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in Best Practical Solutions RT 2.x and 3.x before 3.8.12 and 4.x before 4.0.6 allows remote authenticated users to execute arbitrary SQL commands by leveraging access to a privileged account.

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

## Which versions are affected by CVE-2011-4460?

It affects 1 product.


Products: Bestpractical Rt.

## How do I fix CVE-2011-4460?

Upgrade to a fixed version.

## Is CVE-2011-4460 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5092](https://insights.sbomify.com/CVE-2011-5092/): Privilege escalation in n/a (high 7.5)
- [CVE-2013-3370](https://insights.sbomify.com/CVE-2013-3370/): Missing authorization in n/a (medium 6.8)
- [CVE-2012-4732](https://insights.sbomify.com/CVE-2012-4732/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-2085](https://insights.sbomify.com/CVE-2011-2085/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-4458](https://insights.sbomify.com/CVE-2011-4458/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4460 and fix it if it is affected.

What it is: CVE-2011-4460 is a medium-severity SQL injection vulnerability in n/a, published on 4 Jun 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4460 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-2011-4460/ (Markdown: https://insights.sbomify.com/CVE-2011-4460/index.md)
```

## Sources

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

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