Skip to main content
VulnerabilityPublished

CVE-2026-113442: Extension "TYPO3 Fluid-Form by coding.ms" · Cross-site Scripting

Affects Extension "TYPO3 Fluid-Form by coding.ms"Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 6.0.6 or 5.0.10 when convenient.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.6, 5.0.10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Extension "TYPO3 Fluid-Form by coding.ms" and codingms/fluid-form to 6.0.6 or 5.0.10.

Affected software

ProductAffectedFixed in
Extension "TYPO3 Fluid-Form by coding.ms"codingms/fluid-formAffected
  • >=6.0.0 <6.0.6
Fixed in
  • 6.0.6
Extension "TYPO3 Fluid-Form by coding.ms"codingms/fluid-formAffected
  • <5.0.10
Fixed in
  • 5.0.10
Packagistcodingms/fluid-formpkg:composer/codingms/fluid-formOther threatsAffected
  • >=6.0.0 <6.0.6
  • <5.0.10
Fixed in
  • 6.0.6
  • 5.0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should consider disabling or restricting use of the affected extension versions or applying input sanitization workarounds if feasible.

Description

Values entered by visitors were placed into the HTML summary email without being escaped. An unauthenticated attacker could use this to inject HTML into an email that is shown to the recipient.

References

Community reviews

Loading reviews…