# CVE-2014-9508: Typo3 Open Redirect In Frontend Rendering

> Remote attackers can redirect users to arbitrary domains via crafted anchor links in TYPO3 when specific configuration is enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6xv-rmqc-wcc8

## What is CVE-2014-9508?

CVE-2014-9508 is a medium-severity vulnerability in Typo3 Typo3, published on 4 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The frontend rendering component in TYPO3 4.5.x before 4.5.39, 4.6.x through 6.2.x before 6.2.9, and 7.x before 7.0.2, when config.prefixLocalAnchors is set and using a homepage with links that only contain anchors, allows remote attackers to change URLs to arbitrary domains for those links via unknown vectors.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2014-9508?

6 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 | 4.5.39 |
| `typo3/cms` | Packagist | From 4.5.0 | 4.5.39 |
| `typo3/cms` | Packagist | From 4.6.0 | 6.2.9 |
| `typo3/cms` | Packagist | From 4.6.0 | 6.2.9 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.0.2 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.0.2 |

Products: Typo3 Typo3.

## How do I fix CVE-2014-9508?

Upgrade typo3/cms to a fixed version for your release line: 4.5.39, 6.2.9 or 7.0.2.

## Is CVE-2014-9508 being exploited?

There is no known exploitation of CVE-2014-9508 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-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-2014-9508 and fix it if it is affected.

What it is: CVE-2014-9508 is a medium-severity vulnerability in Typo3 Typo3, published on 4 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-9508 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.39
- typo3/cms (Packagist): affected from 4.5.0; fixed in 4.5.39
- typo3/cms (Packagist): affected from 4.6.0; fixed in 6.2.9
- typo3/cms (Packagist): affected from 4.6.0; fixed in 6.2.9
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.0.2
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.0.2

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

## Sources

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

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