# CVE-2026-121436: Froxlor 2.3.8 before 2.3.15 API Key Disclosure via api_keys.php


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-2qgh-vqj2-gcjx, GHSA-5fm2-8wxf-xc5v

## What is CVE-2026-121436?

CVE-2026-121436 is a high-severity vulnerability in froxlor, published on 3 Nov 2026. 

### Official description

Froxlor from 2.3.8 before 2.3.15 contains an information disclosure vulnerability that allows administrators with customers_see_all to view every account's API key and secret through an unscoped WHERE 1 query in api_keys.php. Attackers can read the super administrator's apikey and secret from the detail modal and replay them to the API to gain super administrator control.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-121436 being exploited?

There is no known exploitation of CVE-2026-121436 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121436 is a high-severity vulnerability in froxlor, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121436 in the wild and no public exploit code.

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-121436/ (Markdown: https://insights.sbomify.com/CVE-2026-121436/index.md)
```

## Sources

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

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