CVE-2026-90935: Froxlor authorization bypass in Mysqls.add API

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

Froxlor is a web hosting control panel that manages customer databases and servers. A flaw in the Mysqls.add API command fails to check whether a customer is authorized to access a particular MySQL server, allowing them to create databases and user accounts on servers they should not have access to—potentially exposing data isolation between customers or accessing premium infrastructure they have not paid for.

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

Quick answers

Is CVE-2026-90935 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-90935 being exploited in the wild.
How severe is CVE-2026-90935?
Medium severity, with a CVSS score of 4.3, published 14 September 2026.
Which products and versions are affected?
Froxlor < 2.3.7; froxlor/froxlor (Packagist) ECOSYSTEM:introduced=0,fixed=2.3.7.
Is there a fix for CVE-2026-90935?
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.
How is CVE-2026-90935 attacked?
It is attacked over the network.
Am I affected by CVE-2026-90935?
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 authorization (CWE-285) in lib/Froxlor/Api/Commands/Mysqls.php. The add() method accepts a customer-controlled mysql_server parameter and validates only that it is numeric and that the server index exists in the configuration. It never cross-references the allowed_mysqlserver allowlist stored in the customer record, a check that is correctly enforced elsewhere (MysqlServer::get(), MysqlServer::listing(), and the UI). An authenticated customer with API access can invoke Mysqls.add with any configured server index, and the API will create a database and MySQL user with attacker-supplied password on the disallowed server. The database record is then inserted into the panel with the attacker's customerid, granting them persistent access via subsequent API calls (Mysqls.get/update/delete). Fix: Froxlor 2.3.7 and later.

Affected products

  • Froxlor Froxlor < 2.3.7

Identifiers

  • CVE-2026-90935
  • GHSA-q4rm-m6xh-5pv7

Timeline

  • 2026-05-29: disclosed
  • 2026-05-29: patched: Froxlor 2.3.7 released

References

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