# CVE-2026-109962: Froxlor 0.10.0 before 2.3.14 Missing Authorization in MysqlServer and Cronjobs API

> Resellers can access admin-only MySQL and cronjob configuration data via API, exposing sensitive management details.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-c54j-3x5v-ch23, GHSA-mx7x-72gh-8j8f

## What is CVE-2026-109962?

CVE-2026-109962 is a medium-severity missing authorization vulnerability in froxlor, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Froxlor 0.10.0 before 2.3.14 contains a missing authorization vulnerability that allows reseller accounts to read full-admin-only MySQL server and cronjob configuration via API read commands. Resellers can call MysqlServer.listing, MysqlServer.get, or Cronjobs.listing through api.php to obtain management usernames, hosts, ports, TLS settings, and cron metadata.

Weakness: CWE-285 (Improper Authorization)

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


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

No fix has been published for CVE-2026-109962 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109962 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109962 is a medium-severity missing authorization vulnerability in froxlor, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109962 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-109962/ (Markdown: https://insights.sbomify.com/CVE-2026-109962/index.md)
```

## Sources

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

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