Skip to main content

TYPO3 Fluid Form CVE-2026-112240

| EUVDEUVD-2026-104869 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-20 TYPO3 GHSA-c6q3-3p3f-392w
6.3
CVSS 4.0 · Vendor: TYPO3
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site using vulnerable form extension
  2. Exploit
    Predict download token and guess file name
  3. Execution
    Request file download URL unauthenticated
  4. Impact
    Retrieve another visitor's uploaded file

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires that the target TYPO3 site runs the coding.ms 'typo3_fluid_form' extension AND uses its file-upload-via-form feature, with at least one file already uploaded by another visitor to retrieve. The attacker must predict or guess both the download token and the uploaded file's name; alternatively, anyone with access to the plain-text body of the generated notification email can read the token directly. Limiting factors: the attack succeeds only against files that exist and whose token/name can be derived (reflected in CVSS AT:P), impact is limited to reading others' uploaded files (low confidentiality, no modification or DoS), and sites not using this extension's upload workflow are unaffected.

Impact

This is a medium-severity information-disclosure flaw (vendor CVSS 4.0 base 6.3) rather than a top-priority emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N) shows a network, unauthenticated vector with low complexity but an attack requirement (AT:P) - meaning exploitation depends on conditions outside the attacker's control, consistent with needing to predict/guess tokens and file names and only succeeding against files that actually exist. Impact is confined to low confidentiality (VC:L); there is no integrity or availability impact. There is no EPSS score, no CISA KEV listing, and no public POC in the provided intelligence, so this reflects no public exploit identified at time of analysis. The combination of only-low confidentiality impact, a probabilistic attack requirement, and the fact that the affected software is a single third-party TYPO3 extension (not a core product) means real-world risk is modest and most likely opportunistic/targeted rather than mass-exploitable. Note a minor signal tension: AC:L advertises easy exploitation, but AT:P and the description's emphasis on token/filename guessing indicate practical exploitation is not fully deterministic - treat 'low complexity' with that caveat.

Exploit ScenarioDerived

A visitor submits a web form that uploads a file via the coding.ms 'typo3_fluid_form' TYPO3 extension; the extension generates a download link protected only by a predictable token, and the filename in the request is not robustly verified. An unauthenticated attacker predicts or guesses the token and file name (or reads the token from the plain-text version of the notification email) and retrieves files uploaded by other visitors. No public exploit code is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 20, 2026

Unauthenticated information disclosure in the coding.ms 'typo3_fluid_form' extension for TYPO3 lets remote attackers retrieve files other visitors uploaded through forms, because the download link depends on a predictable token and the file name in the request is not verified in a guess-resistant way. Only sites that run the extension and use its file-upload-via-form workflow are exposed, and only files that already exist can be read; the vendor rates the issue CVSS 4.0 base 6.3, while our independent assessment scores it CVSS 3.1 6.5-equivalent at AV:N/AC:H/PR:N/UI:N with low confidentiality impact and no integrity or availability effect. A second exposure path exists: the token is rendered in plain text in the text/plain body of the notification email, so anyone who can read that message (forwarding, misdelivery, mailbox compromise, mailing-list archiving) obtains the token directly. No public exploit code or confirmed active exploitation was identified in the provided data.

RemediationAI

No vendor-released patch version is identified in the provided data, so the first action is to consult the TYPO3 extension advisory TYPO3-EXT-SA-2026-033 (https://typo3.org/security/advisory/typo3-ext-sa-2026-033) for the fixed extension release and update typo3_fluid_form to that version through Composer, then flush the TYPO3 caches. If an update cannot be applied immediately, use these compensating controls and accept their trade-offs: disable the file-upload field or the entire form-upload workflow in the extension (removes the exposure but breaks a user-facing feature); move uploaded files outside the web root and serve them only through a controller that enforces a server-side ownership/session check rather than a name-plus-token pair (requires custom development and retesting); replace predictable tokens with cryptographically random values of at least 128 bits and bind them server-side to the specific upload record so file names in the request are never trusted as authorization (requires code changes to the extension); remove the download token from the text/plain part of the notification email, or replace it with a one-time link that expires and is bound to the recipient (reduces the mail-leakage channel, though recipients who forward HTML mail still expose the link); and restrict access to the download endpoint via web-server rules or TYPO3 routing until patched (may block legitimate download links for visitors). Because the vector is unauthenticated and network-reachable, also review web-server and TYPO3 logs for enumeration-style requests against the extension's download endpoint to detect attempts against already-uploaded files.

Affected VersionsENISA

Extension "TYPO3 Fluid-Form by coding.ms" 6.0.0 <6.0.6
Extension "TYPO3 Fluid-Form by coding.ms" 0 <5.0.10

Affected Packages

euvd extension_typo3_fluid_form_by_coding_ms fix: 5.0.10, 6.0.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause maps to CWE-639 (Authorization Bypass Through User-Controlled Key), the classic insecure direct object reference pattern: the download handler treats an attacker-supplied key - here the file name plus a download token - as sufficient proof that the requester is entitled to the file. Two design weaknesses combine. First, the token is derived from a predictable value rather than a cryptographically random identifier, so an attacker who can observe or model the token-generation scheme can compute candidate tokens. Second, the file name submitted in the request is validated in a way that does not resist guessing, meaning an attacker can enumerate or infer plausible names instead of needing the exact stored name. The download endpoint is reachable without authentication (CVSS vector PR:N, AV:N), so no account on the TYPO3 instance is required. The vendor's CVSS 4.0 vector sets AT:P (attack requirements present), reflecting that the attack only succeeds when a matching uploaded file exists and the token/name pair can actually be derived; our independent CVSS 3.1 assessment captures the same constraint through AC:H. Impact is confined to confidentiality (VC:L) - reading other visitors' uploaded files - with no modification, denial of service, or scope change. The plaintext token in the notification email's text part is a separate leakage channel that effectively removes the prediction step for anyone with access to that message, which is why token handling in mail templates must be treated as part of the vulnerability surface, not an operational detail.

Know when Typo3 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TYPO3) PRIMARY 6.3 MEDIUM
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
vuln.today AI 3.7 LOW

Network and unauthenticated (AV:N/PR:N), but AC:H because success depends on predicting tokens/filenames and a matching file existing; only low confidentiality impact, no integrity/availability.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TYPO3).

CVSS VectorVendor: TYPO3

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 20, 2026 - 11:02 EUVD

DescriptionCVE.org

The download link for files uploaded through a form relied on a token that could be predicted. The file name in the request was also not verified in a way that resisted guessing. An unauthenticated attacker could use this to access files uploaded by other visitors. In addition, the token was shown in plain text in the text version of the notification email.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
single third-party TYPO3 extension from one vendor, niche footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Typo3

View all
CVE-2020-15086 CRITICAL POC
9.8 Jul 29

In TYPO3 installations with the "mediace" extension from version 7.6.2 and before version 7.6.5, it has been discovered

CVE-2026-77136 CRITICAL POC
9.5 Aug 25

Server-side template injection in the TYPO3 'Powermail' extension lets an anonymous user submit Fluid template syntax th

CVE-2017-14251 HIGH POC
8.8 Sep 11

Unrestricted File Upload vulnerability in the fileDenyPattern in sysext/core/Classes/Core/SystemEnvironmentBuilder.php i

CVE-2026-46725 CRITICAL POC
9.2 May 19

Remote code execution in the TYPO3 'Content Element Selector' extension allows unauthenticated attackers to execute arbi

CVE-2014-9509 HIGH POC
7.5 Jan 04

The frontend rendering component in TYPO3 4.5.x before 4.5.39, 4.6.x through 6.2.x before 6.2.9, and 7.x before 7.0.2, w

CVE-2026-19418 HIGH POC
7.3 Aug 11

Broken referrer enforcement in TYPO3 CMS backend and Install Tool allows an attacker with JavaScript execution capabilit

CVE-2016-4056 MEDIUM POC
6.1 Jan 23

Cross-site scripting (XSS) vulnerability in the Backend component in TYPO3 6.2.x before 6.2.19 allows remote attackers t

CVE-2023-24814 MEDIUM POC
6.1 Feb 07

TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. Rated medium

CVE-2020-26227 MEDIUM POC
6.1 Nov 23

TYPO3 is an open source PHP based web content management system. Rated medium severity (CVSS 6.1), this vulnerability is

CVE-2020-26216 MEDIUM POC
6.1 Nov 17

TYPO3 Fluid before versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 and 2.6.10 is vulnerable to Cross-Site Scripting.

CVE-2020-15241 MEDIUM POC
6.1 Oct 08

TYPO3 Fluid Engine (package `typo3fluid/fluid`) before versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 is vul

CVE-2020-8091 MEDIUM POC
6.1 Jan 27

svg.swf in TYPO3 6.2.0 to 6.2.38 ELTS and 7.0.0 to 7.1.0 could allow an unauthenticated, remote attacker to conduct a cr

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy