# CVE-2026-47347: TYPO3 CMS - Open Redirect in Core Utilities > Attackers can redirect users to external sites via flawed URL sanitization, enabling phishing attacks against TYPO3 CMS users. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA: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:** 9 Jun 2026 - **Updated:** 9 Jun 2026 - **Also known as:** GHSA-3p42-w5ch-gg42 ## What is CVE-2026-47347? CVE-2026-47347 is a medium-severity vulnerability in TYPO3 CMS, published on 9 Jun 2026. 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 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. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2026-47347? 10 open source packages ship an affected version, including typo3/cms-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-core` | Packagist | All versions | 10.4.57 | | `typo3/cms-core` | Packagist | All versions | 10.4.57 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 | | `typo3/cms-core` | Packagist | From 14.0.0 | 14.3.3 | ## How do I fix CVE-2026-47347? Upgrade typo3/cms-core to a fixed version for your release line: 10.4.57, 11.5.51, 12.4.46 or 13.4.31. ## Is CVE-2026-47347 being exploited? There is no known exploitation of CVE-2026-47347 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-47347 and fix it if it is affected. What it is: CVE-2026-47347 is a medium-severity vulnerability in TYPO3 CMS, published on 9 Jun 2026. 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-2026-47347 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms-core (Packagist): affected all versions; fixed in 10.4.57 - typo3/cms-core (Packagist): affected all versions; fixed in 10.4.57 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.46 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.46 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.31 - typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3 - typo3/cms-core (Packagist): affected from 14.0.0; fixed in 14.3.3 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-2026-47347/ (Markdown: https://insights.sbomify.com/CVE-2026-47347/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47347 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47347 - OSV: https://osv.dev/vulnerability/CVE-2026-47347 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47347/ Summaries are generated and may contain mistakes; the official description above is the record.