Skip to main content
VulnerabilityPublished

CVE-2026-100714: Froxlor before 2.3.12 does not restrict or escape the system.letsencryptchallengepath setting: unlike sibling settings hardened in GHSA-33mp, the

Affects froxlorSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 2.3.12 : patch froxlor as a priority.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.12
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfroxlor/froxlorpkg:github/froxlor/froxlorOther threatsAffected
  • <=2.3.10
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Froxlor to version 2.3.12 or later, where this vulnerability is fixed. Until then, restrict access to the settings-import API and any administrative interfaces that allow modification of the system.letsencryptchallengepath setting to trusted users only. Monitor for unauthorized changes to settings. Patch status is confirmed fixed in 2.3.12.

Description

Froxlor versions up to and including 2.3.10 have a critical vulnerability where the system.letsencryptchallengepath setting is not properly restricted or escaped. This allows an administrator or any actor able to write settings to inject arbitrary command-line options into the acme.sh command executed by root via cron, leading to arbitrary command execution or file writes as root. The issue is fixed in version 2.3.12.

References

Community reviews

Loading reviews…