Skip to main content
Menu
CVEs

CVE

TYPO3 CMS Backend missing authorization in online media file creation

Affects TYPO3 CMS 10.0.0 through 14.3.11 when the backend online media feature (YouTube or Vimeo videos) uses the fallback storage (uid 0). Fixed in 14.3.12, 13.4.40, 12.4.52, 11.5.57 and 10.4.63.

CVE-2026-119622EUVD-2026-126974

Written by a model from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. TYPO3 CMS versions 10.0.0 through 10.4.62, 11.0.0 through 11.5.56, 12.0.0 through 12.4.51, 13.0.0 through 13.4.39, or 14.0.0 through 14.3.11. The backend online media (adding YouTube or Vimeo videos) feature is used, with the target folder in the fallback storage (storage uid 0).

Published
Last modified
Reference
Last checked
25/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

TYPO3 CMS's backend online media feature lets any logged-in, low-privileged backend user create files with partly controllable names in the public web root, even without file mounts or module access, because permission checks are skipped for the fallback storage. Reached remotely over the network with a low-privileged backend login, the flaw can be combined with TYPO3-CORE-SA-2026-027 to re-enable the installer and lead to remote code execution.

Original description

The backend endpoint for adding online media (e.g. YouTube or Vimeo videos) accepted a target folder in the fallback storage (storage uid 0), which points to the public web root of the installation. File mount and permission checks are not applied to the fallback storage. As a result, any authenticated, low-privileged backend user, even without file mounts or module access, could create online media files with a partially controllable file name in the public web root.

In combination with TYPO3-CORE-SA-2026-027, this could be used to re-enable the installer on an already configured instance. The installer could then be used to create a new administrator and system maintainer account, which leads to remote code execution.

Who should check

Teams running TYPO3 CMS 10.0.0 to 14.3.11 that let backend users add online media such as YouTube or Vimeo videos.

“Affected Versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11”

news.typo3.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    TYPO3 CMS versions 10.0.0 through 10.4.62, 11.0.0 through 11.5.56, 12.0.0 through 12.4.51, 13.0.0 through 13.4.39, or 14.0.0 through 14.3.11. The backend online media (adding YouTube or Vimeo videos) feature is used, with the target folder in the fallback storage (storage uid 0).
  • Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119622 (TYPO3 CMS - Missing Authorization in Online Media Handling), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119622 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-backend: from 14.0.0, fixed in 14.3.12; from 13.0.0, fixed in 13.4.40; from 12.0.0, fixed in 12.4.52; from 11.0.0, fixed in 11.5.57; from 10.0.0, fixed in 10.4.63
Fixed versions: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.
Conditions (all must be true for the bug to be hit):
- TYPO3 CMS versions 10.0.0 through 10.4.62, 11.0.0 through 11.5.56, 12.0.0 through 12.4.51, 13.0.0 through 13.4.39, or 14.0.0 through 14.3.11. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-026)
- The backend online media (adding YouTube or Vimeo videos) feature is used, with the target folder in the fallback storage (storage uid 0). (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-026)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-119622 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119622 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-026
- https://github.com/TYPO3/typo3/commit/f342b4d7aa1f6c058f09f69eb8db17f22b0a550b
- https://github.com/TYPO3/typo3/commit/25cb4a81386de21a31aaf4bc89fcf5ebcac71904
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119622
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119622"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • From 14.0.0 · fixed in 14.3.12; From 13.0.0 · fixed in 13.4.40; From 12.0.0 · fixed in 12.4.52; From 11.0.0 · fixed in 11.5.57; From 10.0.0 · fixed in 10.4.63

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Patch
  2. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119622

Is CVE-2026-119622 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Any authenticated backend user with low privileges, even without file mounts or module access, can create online media files with a partly controllable file name in the public web root. Combined with TYPO3-CORE-SA-2026-027, this can re-enable the installer and lead to remote code execution.Source: news.typo3.com

Which versions are affected by CVE-2026-119622?

typo3/cms-backend (Packagist): from 14.0.0 before 14.3.12; from 13.0.0 before 13.4.40; from 12.0.0 before 12.4.52; from 11.0.0 before 11.5.57; from 10.0.0 before 10.4.63.Source: cve.now feed data

Am I affected, and how do I check?

The affected versions are 10.0.0 through 10.4.62, 11.0.0 through 11.5.56, 12.0.0 through 12.4.51, 13.0.0 through 13.4.39, and 14.0.0 through 14.3.11. The bug involves the backend online media feature for adding YouTube or Vimeo videos when the target folder is in the fallback storage (storage uid 0). To check a site, compare its installed TYPO3 version with these ranges and see whether that feature is used with storage uid 0.Source: news.typo3.com

How do I fix CVE-2026-119622?

Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63. The vendor's advisory also recommends 10.4.63 ELTS or 11.5.57 ELTS or 12.4.52 ELTS or 13.4.40 LTS or 14.3.12 LTS or later.Source: cve.now feed data, news.typo3.com

More CVEs