Skip to main content
VulnerabilityPublished

CVE-2026-120329: TYPO3 Extension "Mail" · Injection

Affects TYPO3 Extension "Mail"Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.2.0 or 3.12.5 when convenient.

Data as of 3 Nov 2026, 11:11 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (TYPO3)CVSS 4.05.3
Patch
Available – fixed in 4.2.0, 3.12.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 3 Nov 2026.

What to do

Upgrade Extension "Mail" and mediaessenz/mail to 4.2.0 or 3.12.5.

Affected software

ProductAffectedFixed in
Extension "Mail"mediaessenz/mailAffected
  • >=4.0.0 <4.2.0
Fixed in
  • 4.2.0
Extension "Mail"mediaessenz/mailAffected
  • <3.12.5
Fixed in
  • 3.12.5
Packagistmediaessenz/mailpkg:composer/mediaessenz/mailOther threatsAffected
  • >=4.0.0 <4.2.0
  • <3.12.5
Fixed in
  • 4.2.0
  • 3.12.5

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

AI-suggested

Upgrade to TYPO3 Extension "Mail" version 3.12.5 or later, or 4.2.0 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

CVE-2026-120329 is a medium severity vulnerability in the TYPO3 Extension "Mail" that allows backend users with access to the mail module to write arbitrary page TSconfig. This occurs because the configuration saving process does not restrict submitted settings to valid module options, leading to injection of arbitrary configuration.

References

Community reviews

Loading reviews…