How severe is GHSA-6c46-p6j5-3f49?

No CVSS score has been assigned to GHSA-6c46-p6j5-3f49 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6c46-p6j5-3f49?

GHSA-6c46-p6j5-3f49 affects the following packages: typo3/cms-redirects (Packagist), typo3/cms-redirects (Packagist), typo3/cms-redirects (Packagist), typo3/cms-redirects (Packagist), typo3/cms-redirects (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6c46-p6j5-3f49?

Update typo3/cms-redirects to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c46-p6j5-3f49 is resolved across your whole dependency graph.

How do I detect GHSA-6c46-p6j5-3f49 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-redirects, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6c46-p6j5-3f49 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6c46-p6j5-3f49?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6c46-p6j5-3f49 can be triaged on real exposure rather than presence alone.

Is GHSA-6c46-p6j5-3f49 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6c46-p6j5-3f49 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6c46-p6j5-3f49?

GHSA-6c46-p6j5-3f49 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6c46-p6j5-3f49?

GHSA-6c46-p6j5-3f49 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6c46-p6j5-3f49 published, and has it been updated?

GHSA-6c46-p6j5-3f49 was published on January 13, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-6c46-p6j5-3f49 — typo3/cms-redirects

Fix: TYPO3/typo3@8a46abd

GHSA-6c46-p6j5-3f49 is a CWE-862 vulnerability in typo3/cms-redirects. A fix is available for typo3/cms-redirects — see the affected versions and patch details below.

TYPO3 CMS Allows Broken Access Control in Redirects Module

Also known asCVE-2025-59021

Published

Jan 13, 2026

Updated

Feb 3, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6c46-p6j5-3f49.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

5 pkgs affected

🐘typo3/cms-redirects🐘typo3/cms-redirects🐘typo3/cms-redirects🐘typo3/cms-redirects🐘typo3/cms-redirects

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Problem

Backend users with access to the redirects module and write permission on the sys_redirect table were able to read, create, and modify any redirect record - without restriction to the user’s own file‑mounts or web‑mounts. This allowed attackers to insert or alter redirects pointing to arbitrary URLs - facilitating phishing or other malicious redirect attacks.

Solution

Update to TYPO3 versions 10.4.55 ELTS, 11.5.49 ELTS, 12.4.41 LTS, 13.4.23 LTS, 14.0.2 that fix the problem described.

Credits

Thanks to Georg Dümmler for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.

References

TYPO3-CORE-SA-2026-002

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-redirects`	≥ 14.0.0&&< 14.0.2	14.0.2`composer require typo3/cms-redirects:^14.0.2`
🐘Packagist	`typo3/cms-redirects`	≥ 13.0.0&&< 13.4.23	13.4.23`composer require typo3/cms-redirects:^13.4.23`
🐘Packagist	`typo3/cms-redirects`	≥ 12.0.0&&< 12.4.41	12.4.41`composer require typo3/cms-redirects:^12.4.41`
🐘Packagist	`typo3/cms-redirects`	≥ 11.0.0&&< 11.5.49	11.5.49`composer require typo3/cms-redirects:^11.5.49`
🐘Packagist	`typo3/cms-redirects`	≥ 10.0.0&&< 10.4.55	10.4.55`composer require typo3/cms-redirects:^10.4.55`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-redirects, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-redirects to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c46-p6j5-3f49 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6c46-p6j5-3f49 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6c46-p6j5-3f49. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem Backend users with access to the redirects module and write permission on the `sys_redirect` table were able to read, create, and modify any redirect record - without restriction to the user’s own file‑mounts or web‑mounts. This allowed attackers to insert or alter redirects pointing to arbitrary URLs - facilitating phishing or other malicious redirect attacks. ### Solution Update to TYPO3 versions 10.4.55 ELTS, 11.5.49 ELTS, 12.4.41 LTS, 13.4.23 LTS, 14.0.2 that fix the problem described. ### Credits Thanks to Georg Dümmler for reporting this issue, and to TYPO3 security team m

O3 Security · Impact-Aware SCA

Is GHSA-6c46-p6j5-3f49 in your dependencies?

O3 Security finds GHSA-6c46-p6j5-3f49 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works