Skip to main content
← Vulnerabilities

Broken Access Control in extension "Mail" (mail)

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.2.0, 3.12.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.2.0, 3.12.5.

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach10/20Affects Packagist packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

CVE-2026-120329 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Extension "Mail"; fixed in 4.2.0 and 3.12.5.

Published
Last modified
Published
Not listed in CISA KEV
0.40% · 33rd percentile
18/100 · provisional
Fix
Fixed in 4.2.0, 3.12.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The "Mail" extension (mail) for TYPO3 CMS is affected. Backend users who have access to the mail module can save arbitrary page TSconfig through its configuration form, because submitted settings are not restricted to the module's own options, which bypasses intended access controls.

Read the original description

Saving the configuration of the mail backend module writes submitted settings to the page TSconfig without restricting them to the configuration options of the module. Backend users with access to the mail module can write arbitrary page TSconfig.

What to do

  • Upgrade to a fixed version: 4.2.0, 3.12.5.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • mediaessenz/mailPackagist

    From 4.0.0 · fixed in 4.2.0; fixed in 3.12.5

Evidence 1

  1. Advisory

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120329

Is CVE-2026-120329 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

Which versions are affected by CVE-2026-120329?

mediaessenz/mail (Packagist): from 4.0.0 before 4.2.0; before 3.12.5.Source: cve.now feed data

How do I fix CVE-2026-120329?

Upgrade to a fixed version: 4.2.0, 3.12.5.Source: cve.now feed data