CVE-2026-90936

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory published 2026-09-14. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Froxlor before 2.3.7 fails to properly scope sender alias lookups to the current customer in customer_email.php. Authenticated attackers can enumerate global sender alias IDs and read other customers' allowed sender values by supplying arbitrary senderid parameters in delete confirmation requests.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 14, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github.
Web page

Froxlor before 2.3.7 Information Disclosure via customer_email.php | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.7-information-disclosure-via-customer-email-php
GitHub advisoryMentions a patch (unverified)

Authenticated customers can read other customers' allowed sender aliases · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-mr9h-45p9-fg8h

Vendor Advisories for CVE-2026-90936(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
froxlor/froxlor0.10.0 ... 2.3.6 (108 versions)
  • every version up to 2.3.7: fixed in 2.3.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 84× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 85 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-12 14:46 UTCEG score recompute
  4. 2026-10-11 19:13 UTCEG score recompute
  5. 2026-10-11 16:30 UTCEG score recompute
  6. 2026-10-11 16:07 UTCEG score recompute
  7. 2026-10-11 16:07 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-11 13:45 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-10 16:19 UTCEG score recompute
  12. 2026-10-10 16:19 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  13. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-09 16:23 UTCEG score recompute
  15. 2026-10-09 16:23 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  16. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-08 16:33 UTCEG score recompute
  18. 2026-10-08 16:33 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  19. 2026-10-08 15:38 UTCEG score recompute
  20. 2026-10-08 15:38 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  21. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-07 19:13 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  23. 2026-10-06 16:15 UTCEG score recompute
  24. 2026-10-06 16:14 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 59 more
  1. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-05 16:23 UTCEG score recompute
  3. 2026-10-05 16:23 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-04 16:35 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  6. 2026-10-03 16:46 UTCEG score recompute
  7. 2026-10-03 16:46 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  8. 2026-10-02 16:57 UTCEG score recompute
  9. 2026-10-02 16:57 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  10. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-01 17:09 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  12. 2026-09-30 17:14 UTCEG score recompute
  13. 2026-09-30 17:14 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  14. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-29 16:16 UTCEG score recompute
  16. 2026-09-29 16:16 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  17. 2026-09-28 16:26 UTCEG score recompute
  18. 2026-09-28 16:26 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  19. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-27 16:37 UTCEG score recompute
  21. 2026-09-27 16:37 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  22. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-09-26 16:49 UTCEG score recompute
  24. 2026-09-26 16:49 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  26. 2026-09-25 17:00 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  27. 2026-09-24 17:11 UTCEG score recompute
  28. 2026-09-24 17:11 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  31. 2026-09-23 17:22 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  32. 2026-09-22 20:30 UTCEG score recompute
  33. 2026-09-22 20:30 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  34. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  35. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-09-21 20:41 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  37. 2026-09-20 20:53 UTCEG score recompute
  38. 2026-09-20 20:53 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  39. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-19 21:04 UTCEG score recompute
  41. 2026-09-19 21:04 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  42. 2026-09-18 21:15 UTCEG score recompute
  43. 2026-09-18 21:15 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  44. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-17 21:01 UTCEG score recompute
  46. 2026-09-17 21:01 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  47. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-09-16 21:12 UTCEG score recompute
  49. 2026-09-16 21:12 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  50. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  51. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-09-15 21:22 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  53. 2026-09-14 21:33 UTCEG score recompute
  54. 2026-09-14 21:33 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  55. 2026-09-14 20:35 UTCEG score recompute
  56. 2026-09-14 20:35 UTCGHSA enrichmentGHSA-wc79-h887-58h9 · GitHub CVSS 4.3
  57. 2026-09-14 13:28 UTCEG score recompute
  58. 2026-09-14 13:00 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  59. 2026-09-14 12:59 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-90936?
CVE-2026-90936 is a medium-severity vulnerability; its CVE record was published on September 14, 2026. Froxlor before 2.3.7 fails to properly scope sender alias lookups to the current customer in customer_email.php. Authenticated attackers can enumerate global sender alias IDs and read other customers' allowed sender values by supplying arbitrary senderid parameters in delete confirmation requests.
When was CVE-2026-90936 made public?
CVE-2026-90936 was made public on May 29, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-90936 actively exploited?
CVE-2026-90936 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90936?
CVE-2026-90936 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90936?
A fix for CVE-2026-90936 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90936 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90936

Explore →

Is Your Infrastructure Affected by CVE-2026-90936?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs