Read the docs

Froxlor before 2.3.12 Command Injection via letsencryptchallengepath

Priority MEDIUM 43CWE-88Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-88.

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00549 46th percentileScored 2026-11-07
Fix Fixed froxlor (froxlor): 2.3.12

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
froxlorfroxlorbefore 2.3.122.3.12Patch availableCNA
  • froxlor Vendorfroxlor Affected before 2.3.12 Fixed in 2.3.12 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:*——froxlor
  • cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:* Versions — — ·froxlor

Remediation

  • Fix · CNA froxlor (froxlor) Fixed in 2.3.12

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    froxlor 2.3.12

    11 records Highest priority Priority HIGH 3 HIGH, 3 MEDIUM, 5 LOW

    Other records, highest priority first

    • TI-2026-64867 froxlor before 2.3.12 Authentication Bypass via Session PersistencePriority HIGH 77
    • TI-2026-64872 Froxlor before 2.3.12 Privilege Escalation via SymlinkPriority HIGH 76
    • TI-2026-64871 Froxlor before 2.3.12 Arbitrary File Deletion via SymlinkPriority HIGH 72

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-100714
  2. 2026-10-03 Alias added: GHSA-fh3h-q9pj-x5qp

References

  • TI-2023-00300 Command Injection in froxlor/froxlor CVSS 3.1HIGH 8.8
  • TI-2023-02973 Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor CVSS 3.1CRITICAL 9.8
  • TI-2023-01234 Authentication Bypass by Primary Weakness in froxlor/froxlor CVSS 3.1CRITICAL 9.8
  • TI-2023-01911 Unrestricted Upload of File with Dangerous Type in froxlor/froxlor CVSS 3.1HIGH 8.8
  • TI-2026-64867 froxlor before 2.3.12 Authentication Bypass via Session Persistence CVSS 4.0HIGH 8.7
  • TI-2026-76945 Symlink following in Froxlor enables root privilege escalation CVSS 4.0CRITICAL 9.4
See all 86 →

Sources