GHSA-mr9h-45p9-fg8h: Froxlor Authenticated Customers Can Read Other Vulnerability
MODERATEGHSA-mr9h-45p9-fg8h is a MODERATE (CVSS 4.3) authenticated customers can read other vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Froxlor libraries in the Packagist ecosystem. The issue involves authenticated customers can read other customers' allowed sender aliases. Remediation is available by upgrading affected packages to version 2.3.7.
GHSA-mr9h-45p9-fg8h at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix GHSA-mr9h-45p9-fg8h
To remediate this vulnerability, upgrade all affected Froxlor dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade froxlor/froxlor to 2.3.7
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for froxlor/froxlor
How to Check if You Are Affected
To determine whether your application is affected by GHSA-mr9h-45p9-fg8h, inspect your project dependencies for Froxlor:
inspect dependencies for froxlor/froxlor
Analyze the terminal output to locate any version of Froxlor in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.7), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Froxlor, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-mr9h-45p9-fg8h Affected Froxlor Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
froxlor/froxlor
|
Packagist |
< 2.3.7
|
2.3.7
|
References
Frequently Asked Questions
What is GHSA-mr9h-45p9-fg8h?
Which Froxlor versions are affected?
What version fixes GHSA-mr9h-45p9-fg8h?
Is froxlor/froxlor affected?
What is the CVSS score of GHSA-mr9h-45p9-fg8h?
What CWE is associated with GHSA-mr9h-45p9-fg8h?
How can I check Packagist dependencies for GHSA-mr9h-45p9-fg8h?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mr9h-45p9-fg8h",
"modified" : "2026-07-02T19:23:31Z",
"published" : "2026-07-02T19:23:31Z",
"aliases" : [ ],
"summary" : "Froxlor: Authenticated customers can read other customers' allowed sender aliases",
"details" : "## Summary\n\nAn 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.\n\n## Details\n\nThe vulnerable read lives in `customer_email.php`:\n\n```php\n$senderid = Request::any('senderid', 0);\n...\n$sel_stmt = Database::prepare(\"SELECT `allowed_sender` FROM `\" . TABLE_MAIL_SENDER_ALIAS . \"` WHERE `id` = :sid\");\n$sender_data = Database::pexecute_first($sel_stmt, ['sid' => $senderid]);\n\nHTML::askYesNo('email_reallydelete_sender', $filename, [\n 'id' => $id,\n 'senderid' => $senderid,\n 'page' => $page,\n 'domainid' => $email_domainid,\n 'action' => $action\n], $idna_convert->decode($result['email_full']) . ' -> ' . $sender_data['allowed_sender']);\n```\n\nThe 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:\n\n```sql\nCREATE TABLE `mail_sender_aliases` (\n `id` int(11) NOT NULL auto_increment,\n `email` varchar(255) NOT NULL,\n `allowed_sender` varchar(255) NOT NULL,\n PRIMARY KEY (`id`)\n)\n```\n\nThat 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.\n\n## Proof of Concept\n\nVerified against Froxlor `2.3.6` on a fresh test install with `mail.enable_allow_sender=1`.\n\n1. Create two customers, `victim` and `attacker`.\n2. Give each customer one mailbox.\n3. Add a sender alias for the victim mailbox:\n\n```text\ninfo@victim.local -> leaked-sender@example.org\n```\n\n4. 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:\n\n```text\n/customer_email.php?page=senders&domainid=4&action=delete&id=2&senderid=1\n```\n\nObserved in the live test instance:\n\n```text\nDo you really want to delete the allowed sender info@attacker.local -> leaked-sender@example.org?\n```\n\nThe attacker-controlled mailbox identifier stayed `info@attacker.local`, but the disclosed sender alias text came from the victim-owned row identified by `senderid=1`.\n\n## Impact\n\nAn 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.\n\n## Recommended Fix\n\nScope 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()`.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "froxlor/froxlor"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.3.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.3.6"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/froxlor/froxlor/security/advisories/GHSA-mr9h-45p9-fg8h"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/froxlor/froxlor"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-02T19:23:31Z",
"nvd_published_at" : null
}
}