Froxlor before 2.3.12 Command Injection via letsencryptchallengepath (CVE-2026-100714) | HOL Guard CVE

Critical · CVSS 9.4CVE-2026-100714

Froxlor before 2.3.12 Command Injection via letsencryptchallengepath

Answer in brief

CVE-2026-100714 records a Critical severity (CVSS 9.4) vulnerability in Froxlor before 2.3.12 Command Injection via letsencryptchallengepath. The current sources do not mark it as known exploited. The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 26, 2026Updated Sep 26, 2026Source checked Sep 26, 2026First seen by HOL Sep 26, 2026Material review Sep 26, 2026

Upstream Advisory

Key facts

Risk: Critical · CVSS 9.4
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps froxlor/froxlor (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
froxlor/froxlorgeneric	>=0 <2.3.12	2.3.12

Recommended response

Check inventory. Check lockfiles and deployed manifests for froxlor/froxlor.
Review the reported fix. Update froxlor/froxlor to 2.3.12 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 26, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.