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

> Remote attackers can execute arbitrary SQL commands via the showUid parameter in TYPO3, though the vendor disputes the vulnerability's existence in the core.

- **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:** 10 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-45mh-qx52-cv3c

## What is CVE-2009-4855?

CVE-2009-4855 is a high-severity SQL injection vulnerability in Typo3 Typo3, published on 10 May 2010. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in index.php in TYPO3 4.0 allows remote attackers to execute arbitrary SQL commands via the showUid parameter. NOTE: the TYPO3 Security Team disputes this report, stating that "there is no such vulnerability... The showUid parameter is generally used in third-party TYPO3 extensions - not in TYPO3 Core.

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

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

It affects 1 product.


Products: Typo3 Typo3.

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

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

## Is CVE-2009-4855 being exploited?

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

Public exploit code:

- TYPO3 CMS 4.0 - 'showUid' SQL Injection (exploitdb)

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4855 is a high-severity SQL injection vulnerability in Typo3 Typo3, published on 10 May 2010. It can be exploited 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-4855 exists.

Affected product: Typo3 Typo3. 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-4855/ (Markdown: https://insights.sbomify.com/CVE-2009-4855/index.md)
```

## Sources

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

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