Quick answers
- Is CVE-2026-120332 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120332 being exploited in the wild.
- How severe is CVE-2026-120332?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- MediaEssenz Mail 3.12.4 and below, 4.0.0 to 4.1.0.
- Is there a fix for CVE-2026-120332?
- Yes: fixed in Mail 3.12.5, 4.2.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120332 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120332?
- Check whether you run MediaEssenz Mail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Mail 3.12.5, 4.2.0
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in the Mail extension's backend module where HTML content from emails and tracked URLs are rendered unescaped. An authenticated backend user with mail module access can inject arbitrary HTML and JavaScript payloads that execute in the security context of other backend users. This requires backend access but no network interaction with end users.
Affected products
- mediaessenz Mail 3.12.4 and below, 4.0.0 to 4.1.0
Timeline
- 2026-11-03: disclosed
- 2026-11-03: advisory: TYPO3-EXT-SA-2026-037