Skip to main content
CVE-2026-121435VulnerabilityPublished

Froxlor before 2.3.15 contains an authorization bypass vulnerability that allows authenticated customers to create

Affects froxlorSource GCVE Database

0
Compare
Authoritative record:CVE-2026-121435· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.3.15 when convenient.

Data as of 3 Nov 2026, 16:28 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.14.3
Patch
Available – fixed in 2.3.15
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade froxlor/froxlor to 2.3.15.

Affected software

ProductAffectedFixed in
GitHubfroxlor/froxlorpkg:github/froxlor/froxlorOther threatsAffected
  • <2.3.15
Fixed in
  • 2.3.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Froxlor to version 2.3.15 or later where this authorization bypass vulnerability is fixed. Until patched, administrators should monitor and restrict authenticated user permissions to mitigate unauthorized database creation.

Description

Froxlor versions prior to 2.3.15 have an authorization bypass vulnerability that allows authenticated customers to create MySQL databases even when the feature is disabled by the administrator. This occurs because the Mysqls.add API endpoint does not enforce the customer_hide_options check, enabling unauthorized database creation within the customer's quota despite policy restrictions.

References

Community reviews

Loading reviews…