Skip to main content
Menu
CVEs

CVE

TYPO3 CMS Impexp arbitrary file write in import/export module

Only affects TYPO3 CMS 10.0.0 through 14.x before the fixed releases when importing T3D or XML files in the Import/Export module, which requires an admin backend account. Fixed in 14.3.12, 13.4.40, 12.4.52, 11.5.57 and 10.4.63.

CVE-2026-119621EUVD-2026-126973

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

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

7.7HighCNA
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. Import/Export module used to import a T3D or XML file Attacker needs an admin backend account, or a non-admin backend account with options.impexp.enableImportForNonAdminUser enabled

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

Summary

TYPO3 CMS's Import/Export module has a path traversal flaw that lets a user with a backend login, reached remotely over the network, import a crafted T3D or XML file that writes files with arbitrary content to any location the web server can write to. Such a file, for example a PHP file in the public web root, can lead to remote code execution.

Original description

When importing a T3D or XML file in the Import/Export module, the file hash values of imported files were taken from the import data without validation and used to build the path of a temporary file. A crafted import file could therefore write files with arbitrary content to any location writable by the web server, for example a PHP file in the public web root, which leads to remote code execution. Exploiting this vulnerability requires an administrator backend user account, or a non-admin backend user for whom importing has been enabled via the user TSconfig option options.impexp.enableImportForNonAdminUser.

Who should check

Teams running TYPO3 CMS 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 or 14.0.0-14.3.11 whose backend users can import T3D or XML files.

“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

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity8.7/10CVSS 7.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Import/Export module used to import a T3D or XML file Attacker needs an admin backend account, or a non-admin backend account with options.impexp.enableImportForNonAdminUser enabled
  • 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-119621 (TYPO3 CMS - Path Traversal in Import/Export Module), 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-119621 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-impexp: 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):
- Import/Export module used to import a T3D or XML file (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-025)
- Attacker needs an admin backend account, or a non-admin backend account with options.impexp.enableImportForNonAdminUser enabled (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-025)
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-119621 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119621 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-025
- https://github.com/TYPO3/typo3/commit/365c39a4168f98a5e93bc1cb08a130894fcb8385
- https://github.com/TYPO3/typo3/commit/1f950ddbea861d6775e3074427f82683bdbec2d5
- https://github.com/TYPO3/typo3/commit/db74f64bd64770bd9b8c94e8aea0b633447167ae
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-119621
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-119621"}.

Timeline

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

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

  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 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Patch
  2. Patch
  3. Patch

Corrections

None so far.

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

Questions about CVE-2026-119621

Is CVE-2026-119621 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?

A path traversal flaw in the TYPO3 Import/Export module lets a backend user write files with arbitrary content to any location the web server can write to. An attacker could place a PHP file in the public web root, which can lead to remote code execution.Source: news.typo3.com

Which versions are affected by CVE-2026-119621?

typo3/cms-impexp (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

How do I fix CVE-2026-119621?

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