# CVE-2026-121435: Froxlor before 2.3.15 Authorization Bypass via Mysqls.add API


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-6vjr-55fw-r5x2, GHSA-7fmq-3hpx-jc23

## What is CVE-2026-121435?

CVE-2026-121435 is a medium-severity vulnerability in froxlor, published on 3 Nov 2026. 

### Official description

Froxlor before 2.3.15 contains an authorization bypass vulnerability that allows authenticated customers to create MySQL databases by calling the Mysqls.add API endpoint, which lacks the customer_hide_options check. Customers can invoke Mysqls.add even when the admin has disabled the MySQL feature, creating unauthorized databases within their own quota despite the policy.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-121435?


## How do I fix CVE-2026-121435?

Upgrade froxlor to 2.3.15 or later. The advisory says that version fixes it.

## Is CVE-2026-121435 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121435 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121435 and fix it if it is affected.

What it is: CVE-2026-121435 is a medium-severity vulnerability in froxlor, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121435 exists.

Affected product: froxlor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121435/ (Markdown: https://insights.sbomify.com/CVE-2026-121435/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121435
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121435
- OSV: https://osv.dev/vulnerability/CVE-2026-121435

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121435/
Summaries are generated and may contain mistakes; the official description above is the record.
