# CVE-2026-49742: TYPO3 CMS - Broken Access Control in Media Module > Authenticated backend users can download sensitive files from the server root via the Media Module due to improper path handling. - **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 11 Jun 2026 - **Also known as:** GHSA-chm7-4vch-h8vr ## What is CVE-2026-49742? CVE-2026-49742 is a high-severity path traversal vulnerability in TYPO3 CMS, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose sensitive files such as log files. This issue affects TYPO3 CMS versions 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-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-49742? 16 open source packages ship an affected version, including typo3/cms-core and typo3/cms-filelist. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `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 | | `typo3/cms-filelist` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-filelist` | Packagist | From 11.0.0 | 11.5.51 | | `typo3/cms-filelist` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-filelist` | Packagist | From 12.0.0 | 12.4.46 | | `typo3/cms-filelist` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-filelist` | Packagist | From 13.0.0 | 13.4.31 | | `typo3/cms-filelist` | Packagist | From 14.0.0 | 14.3.3 | | `typo3/cms-filelist` | Packagist | From 14.0.0 | 14.3.3 | ## How do I fix CVE-2026-49742? Upgrade typo3/cms-core to a fixed version for your release line: 11.5.51, 12.4.46, 13.4.31 or 14.3.3. ## Is CVE-2026-49742 being exploited? There is no known exploitation of CVE-2026-49742 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-49742 and fix it if it is affected. What it is: CVE-2026-49742 is a high-severity path traversal vulnerability in TYPO3 CMS, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-49742 in the wild and no public exploit code. Affected packages and fixed versions: - 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 - typo3/cms-filelist (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-filelist (Packagist): affected from 11.0.0; fixed in 11.5.51 - typo3/cms-filelist (Packagist): affected from 12.0.0; fixed in 12.4.46 - typo3/cms-filelist (Packagist): affected from 12.0.0; fixed in 12.4.46 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-49742/ (Markdown: https://insights.sbomify.com/CVE-2026-49742/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49742 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49742 - OSV: https://osv.dev/vulnerability/CVE-2026-49742 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-49742/ Summaries are generated and may contain mistakes; the official description above is the record.