CVE-2026-90935

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Froxlor before 2.3.7 fails to validate the mysql_server parameter against a customer's allowed_mysqlserver allowlist in the Mysqls.add API command. Attackers can supply a disallowed server index to create MySQL databases and users on forbidden servers, bypassing per-customer access controls.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Froxlor before 2.3.7 Authorization Bypass via Mysqls.add API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/froxlor-before-2.3.7-authorization-bypass-via-mysqls-add-api
github Patch Available🟡 PoC Available

Froxlor customer can create MySQL databases on disallowed servers via Mysqls.add API · Advisory · froxlor/froxlor · GitHub

https://github.com/froxlor/froxlor/security/advisories/GHSA-q4rm-m6xh-5pv7

Vendor Advisories for CVE-2026-90935(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 rangeFixed inDependents
froxlor/froxlor0.10.0 ... 2.3.6 (108 versions)2.3.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 23:11 UTCEG score recompute
  3. 2026-09-19 23:11 UTCGHSA enrichment
  4. 2026-09-18 21:37 UTCEG score recompute
  5. 2026-09-18 21:37 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-17 20:04 UTCEG score recompute
  8. 2026-09-17 20:04 UTCGHSA enrichment
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-16 18:29 UTCEG score recompute
  11. 2026-09-16 18:29 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 16:55 UTCEG score recompute
  15. 2026-09-15 16:55 UTCGHSA enrichment
  16. 2026-09-14 13:28 UTCEG score recompute
  17. 2026-09-14 13:00 UTCEG score recompute
  18. 2026-09-14 12:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-90935?
CVE-2026-90935 is a medium vulnerability published on September 14, 2026. Froxlor before 2.3.7 fails to validate the mysqlserver parameter against a customer's allowedmysqlserver allowlist in the Mysqls.add API command. Attackers can supply a disallowed server index to create MySQL databases and users on forbidden servers, bypassing per-customer access controls.
When was CVE-2026-90935 disclosed?
CVE-2026-90935 was first published in the National Vulnerability Database on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90935 actively exploited?
CVE-2026-90935 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.0% of all scored CVEs.
What is the CVSS score of CVE-2026-90935?
CVE-2026-90935 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-90935?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90935, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-90935?

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

Start Free Scan →Browse All CVEs