CVE-2026-47347: TYPO3 CMS - Open Redirect in Core Utilities

Published Jun 9, 2026
·
Updated

Problem Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed the aforementioned sanitization checks. This enables attackers to redirect users to external content and carry out phishing attacks.

Solution Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits TYPO3 CMS thanks Alexandre Romao for reporting this issue, and TYPO3 core & security team member Benjamin Franzke for fixing it.

Resources TYPO3-CORE-SA-2026-009

Other sources

Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed the aforementioned sanitization checks. This enables attackers to redirect users to external content and carry out phishing attacks. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.

NVD

Affected Software

6 affected componentsFixes available
Typo3 TYPO3 CMS<10.4.57, >=11.0.0<=11.5.50, >=12.0.0<=12.4.45, >=13.0.0<=13.4.30, >=14.0.0<=14.3.2
composer/typo3/cms-core>=14.0.0<14.3.3
14.3.3
composer/typo3/cms-core>=13.0.0<13.4.31
13.4.31
composer/typo3/cms-core>=12.0.0<12.4.46
12.4.46
composer/typo3/cms-core>=11.0.0<11.5.51
11.5.51
composer/typo3/cms-core<10.4.57
10.4.57

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 14.3.3
  2. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 13.4.31
  3. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 12.4.46
  4. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 11.5.51
  5. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 10.4.57

Event History

Jun 9, 2026
CVE Published
via MITRE·10:51 AM
Data Sourced
via MITRE·10:51 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Jun 12, 2026
Advisory Published
via GitHub·08:07 PM
Data Sourced
via GitHub·08:07 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47347?

The severity of CVE-2026-47347 is classified as medium with a CVSS score of 5.3.

2

How do I fix CVE-2026-47347?

To fix CVE-2026-47347, you should update your TYPO3 CMS to the latest version that addresses this vulnerability.

3

What type of attack does CVE-2026-47347 enable?

CVE-2026-47347 enables open redirect attacks allowing attackers to redirect users to external malicious content.

4

Which TYPO3 applications are affected by CVE-2026-47347?

Applications that utilize GeneralUtility::sanitizeLocalUrl for local URL validation are vulnerable to CVE-2026-47347.

5

When was CVE-2026-47347 published?

CVE-2026-47347 was published on June 9, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203