CVE-2026-121434
Deferred Deferred - Pending Action

Missing Authorization in Froxlor Certificate Management

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD
CVE-2026-121434
EUVD
EUVD-2026-115856

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
froxlor froxlor 2.3.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Froxlor 2.3.0 before 2.3.15 has a missing authorization check in the Certificates.add and Certificates.update API commands. This allows API users to overwrite Let's Encrypt-managed certificates and private keys with attacker-controlled values. When a REBUILD_VHOST task runs, the malicious certificate is deployed to the web server, breaking HTTPS and disrupting ACME automation.

Detection Guidance

Check Froxlor API logs for unauthorized Certificates.add or Certificates.update requests. Inspect web server configurations for unexpected certificate replacements. Verify Let's Encrypt-managed domains for mismatched certificates.

Impact Analysis

Attackers with API access can replace legitimate certificates with self-signed, expired, or weak ones. This breaks HTTPS for visitors, exposes sensitive data, and desynchronizes ACME automation, causing potential service disruptions and security risks.

Compliance Impact

This vulnerability can lead to non-compliance with GDPR and HIPAA due to broken HTTPS encryption, exposing sensitive data in transit. It may result in unauthorized access to personal or health information, violating confidentiality and integrity requirements.

Mitigation Strategies

Upgrade Froxlor to version 2.3.15 or later. Review API access logs for suspicious activity. Manually verify critical domains' certificates. Restrict API access to trusted users only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-121434. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...