GHSA-mr9h-45p9-fg8h: Froxlor: Authenticated customers can read other customers' allowed sender aliases
Summary An authenticated customer can read other customers' allowed sender aliases from Froxlor's sender-delete confirmation page when mail.enableallowsender is enabled. customeremail.php loads allowedsender 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.
Published Jul 2, 2026
Affected packages
froxlor/froxlor
- Ecosystem
- Composer (PHP)
- Affected
- <= 2.3.6
- Fixed in
- 2.3.7
- Check
composer show froxlor/froxlor
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
The vulnerable read lives in customer_email.php:
$senderid = Request::any('senderid', 0);
...
$sel_stmt = Database::prepare("SELECT `allowed_sender` FROM `" . TABLE_MAIL_SENDER_ALIAS . "` WHERE `id` = :sid");
$sender_data = Database::pexecute_first($sel_stmt, ['sid' => $senderid]);
HTML::askYesNo('email_reallydelete_sender', $filename, [
'id' => $id,
'senderid' => $senderid,
'page' => $page,
'domainid' => $email_domainid,
'action' => $action
], $idna_convert->decode($result['email_full']) . ' -> ' . $sender_data['allowed_sender']);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:
CREATE TABLE `mail_sender_aliases` (
`id` int(11) NOT NULL auto_increment,
`email` varchar(255) NOT NULL,
`allowed_sender` varchar(255) NOT NULL,
PRIMARY KEY (`id`)
)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.
Proof of Concept
Verified against Froxlor 2.3.6 on a fresh test install with mail.enable_allow_sender=1.
- Create two customers,
victimandattacker. - Give each customer one mailbox.
- Add a sender alias for the victim mailbox:
[email protected] -> [email protected]- Log in as the attacker and request the delete-confirmation page for the attacker's own mailbox while supplying the victim's sender alias ID:
/customer_email.php?page=senders&domainid=4&action=delete&id=2&senderid=1Observed in the live test instance:
Do you really want to delete the allowed sender [email protected] -> [email protected]?The attacker-controlled mailbox identifier stayed [email protected], but the disclosed sender alias text came from the victim-owned row identified by senderid=1.
Impact
An authenticated customer can enumerate global sender alias IDs and read other customers' allowed sender values. This is a cross-tenant information disclosure. It does not let the attacker delete the foreign alias because the delete action revalidates ownership.
Recommended Fix
Scope the sender alias lookup to the current customer and mailbox before rendering the confirmation page. The confirmation flow should fetch the sender alias through the same ownership checks used by EmailSender::delete().
--- *Found by aisafe.io*
Credited to adrgs, aisafe-bot.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-54347
Froxlor: Stored XSS in DNS TXT Record Content Allows Customer-to-Admin Account Takeover
high8.7Aug 18, 2026CVE-2026-54348
Froxlor: Second-Order SQL Injection via `Admins.add` `ipaddress` Parameter Allows Full Database Exfiltration
high7.2Aug 18, 2026CVE-2026-54543
Froxlor DomainZones.add allows DNS zone-file RR injection via record/type fields
medium5.4Aug 18, 2026CVE-2026-55593
Froxlor has CSRF Vulnerability in AJAX Endpoint — Missing Cross-Site Request Forgery Protection
medium6.5Aug 18, 2026CVE-2026-62988
Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints
critical9.0Aug 18, 2026GHSA-q4rm-m6xh-5pv7
Froxlor customer can create MySQL databases on disallowed servers via Mysqls.add API
medium4.3Jul 2, 2026
