CVE-2026-100714
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 45% of all known CVEs.
References
Related Vulnerabilities
Other CWE-88 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2016-10033 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2022-36804 | High | 8.8 | 99% | KEV | Fix |
| CVE-2026-24061 | Critical | 9.8 | 99% | KEV | Fix |
| CVE-2007-0882 | High | 10.0 | 98% | - | - |
| CVE-2018-17456 | Critical | 9.8 | 97% | - | Fix |
| CVE-2018-19518 | High | 7.5 | 96% | - | Fix |
Common questions
How do I fix CVE-2026-100714?
No published fix for CVE-2026-100714 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100714 being actively exploited?
Not that we know of. CVE-2026-100714 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.55% is the estimated probability that it will be exploited in the next 30 days. That is higher than 45% of all scored CVEs.
How severe is CVE-2026-100714?
CVE-2026-100714 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100714
Markdown
[](https://tridentstack.com/cve/CVE-2026-100714)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100714"><img src="https://tridentstack.com/cve/badge/CVE-2026-100714.svg" alt="CVE-2026-100714"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-26.