CVE-2026-100714
Deferred Deferred - Pending Action

Command Injection in Froxlor Admin Panel

Publication date: 2026-09-26

Last updated on: 2026-09-26

Assigner: VulnCheck

Description
Froxlor before 2.3.12 does not restrict or escape the system.letsencryptchallengepath setting: unlike sibling settings hardened in GHSA-33mp, the field has no string_regexp or required_otp guard, and its value is concatenated unescaped into the acme.sh command line built in lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php and executed by the root cron via FileDir::safe_exec. Because safe_exec only blacklists shell metacharacters such as ; | & > < \ $ ~ ?, spaces and quotes survive and the value is word-split into additional acme.sh arguments. An administrator, or any actor able to write settings (for example through the settings-import API), can therefore inject acme.sh options such as --renew-hook, --pre-hook or --post-hook to obtain arbitrary command execution as root at the next Let's Encrypt cron run, or use --config-home/--cert-home for arbitrary file writes. Versions up to and including 2.3.10 are affected; the issue is fixed in 2.3.12.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-26
Last Modified
2026-09-26
Generated
2026-09-26
AI Q&A
2026-09-26
EPSS Evaluated
N/A
NVD
CVE-2026-100714
EUVD
EUVD-2026-87687

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
froxlor froxlor to 2.3.10 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-88 The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Froxlor before 2.3.12 has a vulnerability where the system.letsencryptchallengepath setting is not properly restricted or escaped. This setting is concatenated unescaped into the acme.sh command line, allowing an attacker to inject additional arguments. Because of insufficient input validation, spaces and quotes in the setting value are preserved, enabling word splitting into extra acme.sh options like --renew-hook or --pre-hook. This can lead to arbitrary command execution as root during the next Let's Encrypt cron run or allow arbitrary file writes via options like --config-home.

Detection Guidance

Check Froxlor version with 'froxlor --version' or via the web interface. If version is below 2.3.12, the system is vulnerable. Inspect cron jobs for Let's Encrypt tasks and review settings for 'system.letsencryptchallengepath' to detect potential unsafe values.

Impact Analysis

If you use Froxlor versions up to 2.3.10, an attacker with access to write settings (including through the settings-import API) could exploit this to execute arbitrary commands as the root user. This could allow full system compromise, data theft, or unauthorized modifications. The impact includes potential loss of control over the server, exposure of sensitive data, and disruption of services.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, violating compliance requirements under GDPR (e.g., unauthorized processing of personal data) and HIPAA (e.g., unauthorized access to protected health information). Organizations using affected Froxlor versions may face legal penalties, reputational damage, and loss of certification due to failure to maintain adequate security controls.

Mitigation Strategies

Upgrade Froxlor to version 2.3.12 or later immediately. Remove or restrict write access to settings that can modify 'system.letsencryptchallengepath'. Audit all API users with settings import privileges to prevent unauthorized changes.

Chat Assistant

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

EPSS Chart