CVE-2026-120328: TYPO3 Extension "Mail" · Insecure Direct Object Reference
Affects TYPO3 Extension "Mail"Source CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.2.0 or 3.12.5 when convenient.
Data as of 3 Nov 2026, 11:11 UTC
Thin evidence
One scorer or none| CNA (TYPO3) | CVSS 4.0 | 6.9 |
|---|
- Patch
- Available – fixed in 4.2.0, 3.12.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Extension "Mail"mediaessenz/mail | Affected
| Fixed in
|
| Extension "Mail"mediaessenz/mail | Affected
| Fixed in
|
Packagistmediaessenz/mailpkg:composer/mediaessenz/mailOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the TYPO3 Extension "Mail" to version 3.12.5 or later, or 4.2.0 or later, where the vulnerability has been fixed. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-120328 is an authorization bypass vulnerability in the TYPO3 Extension "Mail". The click tracking middleware fails to validate the authentication code of newsletter recipients if the code is omitted. This allows unauthenticated attackers to access personal data of newsletter recipients embedded in email links. The issue affects versions 3.12.5 up to but not including 4.2.0 and versions prior to 3.12.5. A fix is available in versions 4.2.0 and 3.12.5.