Description
Forms using FileUpload or ImageUpload elements with a custom saveToFileMount configured stored uploaded files in the default storage folder 1:/user_upload/ instead of the configured destination. This could cause uploaded files to end up in a publicly accessible storage even though a restricted, non-public storage had been configured. Files stored this way are served directly, without the access checks applied to non-public storages. Forms that use the default value for saveToFileMount are not affected. This issue affects TYPO3 CMS versions 14.0.0-14.3.8.
Published: 2026-10-13
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Public File Exposure
Action: Patch Now
AI Analysis

Impact

A configuration flaw in TYPO3 CMS’s Form Framework causes forms that use FileUpload or ImageUpload elements with a custom saveToFileMount setting to store files in the default storage folder 1:/user_upload/ instead of the intended destination. The default storage is publicly accessible and files placed there are served directly without the normal access checks applied to non‑public storages. As a result, files uploaded through affected forms can be read by anyone with web access, exposing potentially sensitive data, enabling execution of malicious scripts, and bypassing any restrictions that the originally intended storage might have enforced. This is a type of information exposure (CWE‑552) and a failure to enforce access controls (CWE‑696).

Affected Systems

The vulnerability affects TYPO3 CMS releases from 14.0.0 through 14.3.8. Systems that have a secure, non‑public storage configured but rely on a custom saveToFileMount for file uploads can be inadvertently leaking content. Forms that use the default saveToFileMount value are not impacted, but administrators still need to audit custom configurations.

Risk and Exploitability

The CVSS score of 6.3 indicates moderate severity, and the EPSS score is not available, so the exploitation probability is unknown. The vulnerability is not listed in the CISA KEV catalogue. Exploitation requires the attacker to have the ability to influence form configuration—typically an administrative role or a compromised backend—and then to upload files. Once uploaded, the files become publicly accessible because they bypass the usual access control. No publicly documented exploits are known, but the impact of a data disclosure or the ability to host malicious content makes remediation urgent.

Generated by OpenCVE AI on October 13, 2026 at 10:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest TYPO3 CMS update (at minimum 14.3.9) to include the fix that correctly honors the saveToFileMount configuration.
  • Verify all forms that use FileUpload or ImageUpload elements to confirm that their saveToFileMount points to a protected, non‑public storage and not the default 1:/user_upload/.
  • If an update is not yet available, restrict web access to folder 1:/user_upload/ (e.g., via server configuration or .htaccess) or disable the upload feature for untrusted users until the issue is resolved.

Generated by OpenCVE AI on October 13, 2026 at 10:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 17 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Oct 2026 09:15:00 +0000


Tue, 13 Oct 2026 09:45:00 +0000

Type Values Removed Values Added
Description Forms using FileUpload or ImageUpload elements with a custom saveToFileMount configured stored uploaded files in the default storage folder 1:/user_upload/ instead of the configured destination. This could cause uploaded files to end up in a publicly accessible storage even though a restricted, non-public storage had been configured. Files stored this way are served directly, without the access checks applied to non-public storages. Forms that use the default value for saveToFileMount are not affected. This issue affects TYPO3 CMS versions 14.0.0-14.3.8.
Title TYPO3 CMS - Security Misconfiguration in Form Framework
First Time appeared Typo3
Typo3 typo3 Cms
Weaknesses CWE-552
CWE-696
CPEs cpe:2.3:a:typo3:typo3_cms:*:*:*:*:*:*:*:*
Vendors & Products Typo3
Typo3 typo3 Cms
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: TYPO3

Published:

Updated: 2026-10-16T17:17:41.990Z

Reserved: 2026-10-12T12:26:08.379Z

Link: CVE-2026-109162

cve-icon Vulnrichment

Updated: 2026-10-16T17:01:49.655Z

cve-icon NVD

Status : Deferred

Published: 2026-10-13T10:17:15.463

Modified: 2026-10-16T19:56:15.773

Link: CVE-2026-109162

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-13T12:15:14Z

Weaknesses
  • CWE-552

    Files or Directories Accessible to External Parties

  • CWE-696

    Incorrect Behavior Order