# CVE-2026-41232: Froxlor has an Email Sender Alias Domain Ownership Bypass via Wrong Array Index Allows Cross-Customer Email Spoofing

Source: https://junglewise.ai/threats/cve-2026-41232-froxlor-has-an-email-sender-alias-domain-ownership-bypass-via  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-23. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-41232 · Severity: medium · CVSS 5 · Published 2026-04-23

Froxlor is open source server administration software. Prior to version 2.3.6, 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. Version 2.3.6 fixes the issue.

Technologies: [Froxlor](https://junglewise.ai/threats/technologies/froxlor), [froxlor/froxlor (Packagist)](https://junglewise.ai/threats/technologies/froxlor-froxlor). Vendors: [Froxlor](https://junglewise.ai/threats/vendors/froxlor), [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

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

**How severe is CVE-2026-41232?** Medium severity, with a CVSS score of 5, published 23 April 2026.

**Which products and versions are affected?** froxlor/froxlor (Packagist) < 2.3.6, ECOSYSTEM:introduced=0,fixed=2.3.6.

**Is there a fix for CVE-2026-41232?** Yes. froxlor/froxlor (Packagist): upgrade to 2.3.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-41232?** Check whether you run Froxlor or froxlor/froxlor (Packagist) 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

- froxlor/froxlor (Packagist): upgrade to 2.3.6 or later

  ```sh
  composer require froxlor/froxlor:^2.3.6
  ```


## Affected products

- Froxlor
- froxlor/froxlor (Packagist) < 2.3.6, ECOSYSTEM:introduced=0,fixed=2.3.6

## Identifiers

- CVE-2026-41232
- GHSA-vmjj-qr7v-pxm6

## References

- [https://api.github.com/users/offset](https://api.github.com/users/offset)
- [https://github.com/offset](https://github.com/offset)
- [https://api.github.com/users/offset/gists%7B/gist_id%7D](https://api.github.com/users/offset/gists%7B/gist_id%7D)
- [https://api.github.com/users/offset/repos](https://api.github.com/users/offset/repos)
- [https://avatars.githubusercontent.com/u/114768995?v=4](https://avatars.githubusercontent.com/u/114768995?v=4)
- [https://api.github.com/users/offset/events%7B/privacy%7D](https://api.github.com/users/offset/events%7B/privacy%7D)

## Related threats

- [Froxlor information disclosure in API keys listing](https://junglewise.ai/threats/cve-2026-121436-froxlor-from-2-3-8-before-2-3-15-contains-an-information)
- [Froxlor authorization bypass in Mysqls.add API](https://junglewise.ai/threats/cve-2026-121435-froxlor-before-2-3-15-contains-an-authorization-bypass)
- [Froxlor Certificates API authorization bypass in Let's Encrypt management](https://junglewise.ai/threats/cve-2026-121434-froxlor-2-3-0-before-2-3-15-contains-a-missing-authorization)
- [Froxlor symlink following in Statistics::makeChownWithNewStats](https://junglewise.ai/threats/cve-2026-113678-froxlor-before-2-3-15-contains-a-symlink-following-vulnerability)
- [Froxlor missing authorization in SubDomains.delete API](https://junglewise.ai/threats/cve-2026-113677-froxlor-from-0-10-0-before-2-3-15-contains-a-missing)