PT-2026-57599 · Packagist · Froxlor/Froxlor

Published

2026-07-02

·

Updated

2026-07-02

CVSS v3.1

4.3

Medium

VectorAV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

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:
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:
sql
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.
  1. Create two customers, victim and attacker.
  2. Give each customer one mailbox.
  3. Add a sender alias for the victim mailbox:
text
info@victim.local -> leaked-sender@example.org
  1. 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:
text
/customer email.php?page=senders&domainid=4&action=delete&id=2&senderid=1
Observed in the live test instance:
text
Do you really want to delete the allowed sender info@attacker.local -> leaked-sender@example.org?
The attacker-controlled mailbox identifier stayed info@attacker.local, 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

Fix

Information Disclosure

Found an issue in the description? Have something to add? Feel free to write us 👾
dbugs@ptsecurity.com

Weakness Enumeration

CWE-200

Related Identifiers

GHSA-MR9H-45P9-FG8H

Affected Products

Froxlor/Froxlor