# CVE-2011-4614: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via a URL in the BACK_PATH parameter of the TYPO3 workspaces extension.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h857-jmgh-2v5g

## What is CVE-2011-4614?

CVE-2011-4614 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 18 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in Classes/Controller/AbstractController.php in the workspaces system extension in TYPO3 4.5.x before 4.5.9, 4.6.x before 4.6.2, and development versions of 4.7 allows remote attackers to execute arbitrary PHP code via a URL in the BACK_PATH parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Typo3 Typo3.

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

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

## Is CVE-2011-4614 being exploited?

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

Public exploit code:

- Typo3 4.5 < 4.7 - Remote Code Execution / Local File Inclusion / Remote File Inclusion (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-2011-4614 and fix it if it is affected.

What it is: CVE-2011-4614 is a medium-severity code injection vulnerability in Typo3 Typo3, published on 18 Feb 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4614 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-2011-4614/ (Markdown: https://insights.sbomify.com/CVE-2011-4614/index.md)
```

## Sources

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

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