Is CVE-2026-90936 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-90936 being exploited in the wild.

How severe is CVE-2026-90936?

Medium severity, with a CVSS score of 4.3, published 14 September 2026.

Which products and versions are affected?

Froxlor before 2.3.7; froxlor/froxlor (Packagist) ECOSYSTEM:introduced=0,fixed=2.3.7.

Is there a fix for CVE-2026-90936?

Yes. froxlor/froxlor (Packagist): upgrade to 2.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-90936?

Check whether you run Froxlor or froxlor/froxlor (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-90936: Froxlor information disclosure in sender alias lookups

CVE-2026-90936 · Severity: medium · CVSS 4.3 · Published 2026-09-14

Froxlor is a web hosting control panel that manages customer email accounts and sender aliases (approved sender identities). A flaw in the sender alias deletion feature fails to verify that an authenticated customer owns the alias being accessed, allowing customers to view other customers' allowed sender addresses by manipulating request parameters. This enables cross-customer data exposure without requiring additional privileges or user interaction.

Technologies: Froxlor, froxlor/froxlor (Packagist). Vendors: Froxlor, Packagist.

Quick answers

Is CVE-2026-90936 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-90936 being exploited in the wild.
How severe is CVE-2026-90936?: Medium severity, with a CVSS score of 4.3, published 14 September 2026.
Which products and versions are affected?: Froxlor before 2.3.7; froxlor/froxlor (Packagist) ECOSYSTEM:introduced=0,fixed=2.3.7.
Is there a fix for CVE-2026-90936?: Yes. froxlor/froxlor (Packagist): upgrade to 2.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-90936?: Check whether you run Froxlor or froxlor/froxlor (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

froxlor/froxlor (Packagist): upgrade to 2.3.7 or later
```
composer require froxlor/froxlor:^2.3.7
```

Technical details

The vulnerability is an improper access control flaw (CWE-200) in customer_email.php's sender alias deletion confirmation flow. The code retrieves sender alias data using only a global auto-increment ID parameter (senderid) without scoping the query to the current customer or their mailbox. An authenticated customer can enumerate sender alias IDs and craft requests to view foreign aliases by supplying arbitrary senderid values in delete confirmation requests. The allowed_sender value is then disclosed in the HTML confirmation dialog. The actual delete operation does validate ownership, preventing unauthorized deletion, but the confirmation page renders the queried data before that check. Fix: version 2.3.7 and later scope sender alias lookups to the current customer and mailbox before rendering the confirmation.

Affected products

Froxlor Froxlor before 2.3.7

Identifiers

CVE-2026-90936
GHSA-mr9h-45p9-fg8h

Timeline

2026-05-29: disclosed: GitHub Security Advisory (GHSA-mr9h-45p9-fg8h) published
2026-09-14: advisory: CVE-2026-90936 published on NVD
2026: patched: Fixed in Froxlor 2.3.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.