# CVE-2011-3583: Typo3 SQL injection due to faulty prepared statements

> SQL injection in TYPO3 Core allows attackers to manipulate database queries when multiple user-controlled parameters are bound incorrectly.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gx4p-6w86-f8jx

## What is CVE-2011-3583?

CVE-2011-3583 is a critical SQL injection vulnerability in Typo3 Typo3, published on 25 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability. This issue can only be exploited if two or more parameters are bound to the query and at least two come from user input.

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

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

2 open source packages ship an affected version, including typo3/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 4.5.0 to 4.5.5 | None |
| `typo3/cms` | Packagist | From 4.5.0 to 4.5.5 | None |

Products: Typo3 Typo3.

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

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

## Is CVE-2011-3583 being exploited?

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

## 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-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)
- [CVE-2020-15098](https://insights.sbomify.com/CVE-2020-15098/): Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3583 is a critical SQL injection vulnerability in Typo3 Typo3, published on 25 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3583 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 4.5.0 up to 4.5.5; no fix listed
- typo3/cms (Packagist): affected from 4.5.0 up to 4.5.5; no fix listed

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

## Sources

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

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