# CVE-2026-121434: Froxlor 2.3.0 before 2.3.15 Authorization Bypass via Certificates.update API


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-ch7m-649m-x7xg, GHSA-hxjh-8h5v-fp7m

## What is CVE-2026-121434?

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

### Official description

Froxlor 2.3.0 before 2.3.15 contains a missing authorization check in the Certificates.add and Certificates.update API commands, which do not verify whether a domain's certificate is Let's Encrypt-managed. Customers with API access can overwrite the managed certificate and private key with an attacker-chosen pair, which a REBUILD_VHOST task deploys to the webserver, breaking HTTPS and desynchronizing ACME automation.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-121434 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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