Servers and applications
GHSA-mr9h-45p9-fg8h
Authenticated customers can read other customers' allowed sender aliases
- Severity
- Medium 4.3
- Published
- 29 May 2026
- Last changed
- 29 May 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.7
- Weakness
- Information exposure (CWE-200)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N- Sources
- Project advisories (GitHub)
Description
An authenticated customer can read other customers' allowed sender aliases from Froxlor's sender-delete confirmation page when mail.enable_allow_sender is enabled. customer_email.php loads allowed_sender by global auto-increment senderid alone, so a customer can enumerate foreign sender alias IDs and make Froxlor disclose those values in the confirmation dialog for the attacker's own mailbox.
The vulnerable read lives in customer_email.php:
The query does not scope senderid to the current customer or to the mailbox being edited. mail_sender_aliases.id is a global AUTO_INCREMENT primary key:
That makes sender alias IDs enumerable. A customer who owns any mailbox with sender-alias management enabled can request the delete-confirmation page for their own mailbox while supplying foreign senderid values. Froxlor then renders the foreign allowed_sender string in the confirmation prompt.
Affected software
| Software | Affected versions |
|---|---|
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
- GitHub Advisory Database https://github.com/advisories/GHSA-mr9h-45p9-fg8h
- github.com https://github.com/froxlor/froxlor/security/advisories/GHSA-mr9h-45p9-fg8h