froxlor/froxlor

GHSA-MR9H-45P9-FG8H

GHSA-MR9H-45P9-FG8H is a medium-severity security vulnerability in froxlor/froxlor (composer), affecting versions <= 2.3.6. It is fixed in 2.3.7.

Key facts
CVSS score
4.3
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
froxlor/froxlor
Fixed in
2.3.7
Disclosed
Not available

Summary

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. Details The vulnerable read lives in customeremail.php: The query does not scope senderid to the current customer or to the mailbox being edited. mailsenderaliases.id is a global AUTOINCREMENT 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 allowedsender string in the confirmation prompt. Proof of Concept Verified against Froxlor 2.3.6 on a fresh test install with mail.enableallow_sender=1. Create two customers, victim and attacker. Give each customer one mailbox. Add a sender alias for the victim mailbox: 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: Observed in the live test instance: 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

Impact

Severity and exposure

GHSA-MR9H-45P9-FG8H has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2.3.7). Upgrading removes the vulnerable code path.

Affected versions

composer

  • froxlor/froxlor (<= 2.3.6)

Security releases

  • froxlor/froxlor → 2.3.7 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether GHSA-MR9H-45P9-FG8H is reachable in your applications. Explore open-source security for your team.

See if GHSA-MR9H-45P9-FG8H is reachable in your applications. Get a demo

Already deployed Kodem? See GHSA-MR9H-45P9-FG8H in your environment

Remediation advice

Upgrade froxlor/froxlor to 2.3.7 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about GHSA-MR9H-45P9-FG8H

What is GHSA-MR9H-45P9-FG8H?

GHSA-MR9H-45P9-FG8H is a medium-severity security vulnerability in froxlor/froxlor (composer), affecting versions <= 2.3.6. It is fixed in 2.3.7.

How severe is GHSA-MR9H-45P9-FG8H?

GHSA-MR9H-45P9-FG8H has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of froxlor/froxlor are affected by GHSA-MR9H-45P9-FG8H?

froxlor/froxlor (composer) versions <= 2.3.6 is affected.

Is there a fix for GHSA-MR9H-45P9-FG8H?

Yes. GHSA-MR9H-45P9-FG8H is fixed in 2.3.7. Upgrade to this version or later.

Is GHSA-MR9H-45P9-FG8H exploitable, and should I be worried?

Whether GHSA-MR9H-45P9-FG8H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether GHSA-MR9H-45P9-FG8H is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-MR9H-45P9-FG8H?

Upgrade froxlor/froxlor to 2.3.7 or later.

Stop the waste.
Protect your environment with Kodem.