Servers and applications
CVE-2026-41232
Email Sender Alias Domain Ownership Bypass via Wrong Array Index Allows Cross-Customer Email Spoofing
- Severity
- Medium 5.0
- Published
- 15 Apr 2026
- Last changed
- 11 Nov 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.6
- Exploit chance
- 0.2% in the next 30 daysHigher than 14% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N- Also known as
- GHSA-vmjj-qr7v-pxm6
- Sources
- NVD, Project advisories (GitHub)
Description
In EmailSender::add(), the domain ownership validation for full email sender aliases uses the wrong array index when splitting the email address, passing the local part instead of the domain to validateLocalDomainOwnership(). This causes the ownership check to always pass for non-existent "domains," allowing any authenticated customer to add sender aliases for email addresses on domains belonging to other customers. Postfix's sender_login_maps then authorizes the attacker to send emails as those addresses.
In lib/Froxlor/Api/Commands/EmailSender.php at line 100, when a customer adds a full email address (not a @domain wildcard) as an allowed sender, the code splits on @ and takes index [0]:
For input [email protected], explode("@", "[email protected]") returns ["admin", "domain-b.com"]. Index [0] is "admin" — the local part, not the domain.
The validateLocalDomainOwnership() function (lines 346-355) then queries panel_domains for a domain matching "admin":
Affected software
| Software | Affected versions |
|---|---|
FroxlorServers and applications · cpe:a:froxlor:froxlor |
|
FroxlorServers and applications · github:froxlor/froxlor |
|
About Froxlor
The server administration software for your needs - The official Froxlor development Git repository
- Monthly downloads (Packagist)
- 159Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 406Packagist, 15 Nov 2026
- GitHub stars
- 1,752GitHub, 15 Nov 2026
- Forks
- 467GitHub, 15 Nov 2026
- Latest release
- 2.3.17GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- GNU Lesser General Public License, version 2.1Wikidata
- Written in
- PHPWikidata
- First published on GitHub
- 6 Mar 2012GitHub
Vulnerabilities in Froxlor
- In our list
- 97
- Published in the last 12 months
- 56
- Critical, last 12 months
- 6
- High, last 12 months
- 24
- Known exploited
- 0
- CVE-2026-130755Froxlor before 2.3.16 Authorization Bypass via Traffic.listing API CommandMedium 5.3 18 Nov 2026
- CVE-2026-121436Froxlor 2.3.8 before 2.3.15 API Key Disclosure via api_keys.phpHigh 8.6 3 Nov 2026
- CVE-2026-121435Froxlor before 2.3.15 Authorization Bypass via Mysqls.add APIMedium 5.3 3 Nov 2026
- CVE-2026-121434Froxlor 2.3.0 before 2.3.15 Authorization Bypass via Certificates.update APIMedium 5.3 3 Nov 2026
- GHSA-vhfr-xvmw-p2m9Froxlor customer Traffic listing API bypasses the customer_hide_options traffic restrictionMedium 4.3 3 Nov 2026
- CVE-2026-113678Froxlor before 2.3.15 Symlink Following Privilege Escalation via Traffic CronCritical 9.4 20 Oct 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-41232
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41232
- GitHub Advisory Database https://github.com/advisories/GHSA-vmjj-qr7v-pxm6
- github.com https://github.com/froxlor/froxlor/security/advisories/GHSA-vmjj-qr7v-pxm6