# CVE-2026-120330: TYPO3 Mail extension broken access control in backend actions

Source: https://junglewise.ai/threats/cve-2026-120330-backend-actions-and-ajax-routes-of-the-mail-module-do-not-check  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-120330 · Severity: info · Published 2026-11-03

The Mail extension for TYPO3, a PHP-based content management system, fails to properly check whether backend administrators have permission to access specific mail campaigns and recipient groups. An administrator with access to the mail module can view, modify, send, and export mails and recipient lists outside their assigned areas, exposing the personal data of newsletter subscribers and potentially compromising recipient privacy.

Technologies: [MediaEssenz Mail](https://junglewise.ai/threats/technologies/mediaessenz-mail). Vendors: [MediaEssenz](https://junglewise.ai/threats/vendors/mediaessenz).

## Quick answers

**Is CVE-2026-120330 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-120330 being exploited in the wild.

**How severe is CVE-2026-120330?** Informational severity, published 3 November 2026.

**Which products and versions are affected?** MediaEssenz Mail 3.12.4 and below, 4.0.0 - 4.1.0.

**Is there a fix for CVE-2026-120330?** Yes: fixed in 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-120330 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-120330?** 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 3.12.5, 4.2.0

## Technical details

The vulnerability exists in backend actions and AJAX routes within the Mail extension's mail module, which do not validate access control against the web mounts of authenticated backend users. A backend user with mail module access can perform unauthorized operations (view, change, send, export) on mails and recipient groups by directly accessing them through the backend interface, bypassing mount restrictions. This is a broken access control issue requiring authentication but allowing privilege escalation within the backend.

## Affected products

- MediaEssenz Mail 3.12.4 and below, 4.0.0 - 4.1.0

## Timeline

- 2026-11-03: disclosed

## References

- [https://packagist.org/](https://packagist.org/)
- [https://typo3.org/security/advisory/typo3-ext-sa-2026-037](https://typo3.org/security/advisory/typo3-ext-sa-2026-037)

## Related threats

- [TYPO3 Mail extension cross-site scripting in backend](https://junglewise.ai/threats/cve-2026-120332-the-html-content-of-mails-and-tracked-urls-are-rendered)
- [TYPO3 Mail extension authentication bypass in click tracking](https://junglewise.ai/threats/cve-2026-120328-the-click-tracking-middleware-does-not-validate-the)
- [TYPO3 Mail extension open redirection in click tracking](https://junglewise.ai/threats/cve-2026-120327-the-click-tracking-middleware-accepts-an-arbitrary-target-url)