← Back to the live CVE advisory feed

CVE-2026-100714: froxlor

Severity

9.4 (CRITICAL)

Vendor

FROXLOR

Affected versions

0 through before 2.3.12

Fixed version

2.3.12

Patch status

Patched

Published

2026-09-26T14:16:57.240

Modified

2026-09-26T14:16:57.373

Why it matters

Critical vulnerability requiring immediate validation against your environment.

Recommended admin actions

• Prioritize validation immediately due to critical CVSS severity.
• Compare installed versions against the affected version range in the advisory.

Technical summary

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.

View the official NVD record for CVE-2026-100714

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.