Broken Access Control in extension "Mail" (mail)
Affects TYPO3 Extension "Mail" 3.12.4 and below and 4.0.0 to 4.1.0, where backend users with mail module access can reach mails outside their web mounts. Fixed in 3.12.5 and 4.2.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.2.0, 3.12.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected extension versions: 3.12.4 and below, and 4.0.0 - 4.1.0 of the mail extension. Backend user has access to the mail module.
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 if CISA's SSVC rates it automatable
CVE-2026-120330 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Extension "Mail"; fixed in 4.2.0 and 3.12.5.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.38% · 32nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 4.2.0, 3.12.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The "Mail" extension for TYPO3 CMS, which manages newsletters and mail content, is affected. Backend users who have access to the mail module can view, change, send, and export mails and recipient groups located outside their permitted web mounts, including recipients' personal data.
Read the original description
Backend actions and ajax routes of the mail module do not check whether the backend user has access to the page of the requested mail or recipient group. Backend users with access to the mail module can view, change, send and export mails and recipient groups outside their web mounts, including the personal data of recipients.
What to do
Check whether your setup matches what the bug needs.
Affected extension versions: 3.12.4 and below, and 4.0.0 - 4.1.0 of the mail extension. Backend user has access to the mail module.Upgrade to a fixed version: 4.2.0, 3.12.5.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- mediaessenz/mailPackagist
From 4.0.0 · fixed in 4.2.0; fixed in 3.12.5
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120330
Is CVE-2026-120330 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Backend users who have access to the mail module can view, change, send and export mails and recipient groups that lie outside their assigned web mounts. This includes the personal data of recipients.Source: news.typo3.com
Which versions are affected by CVE-2026-120330?
mediaessenz/mail (Packagist): from 4.0.0 before 4.2.0; before 3.12.5.Source: cve.now feed data
Am I affected, and how do I check?
Versions 3.12.4 and below, and 4.0.0 through 4.1.0, of the TYPO3 mail extension are affected, and the issue concerns backend users with access to the mail module. You can check your installed version of the mail extension in the TYPO3 extension manager or with composer show typo3/mail.Source: news.typo3.com
How do I fix CVE-2026-120330?
Update the mail extension to 3.12.5 if you are on the 3.x line, or to 4.2.0 if you are on the 4.x line. Updated versions are available from the TYPO3 extension manager and packagist.Source: news.typo3.com