Quick answers
- Is CVE-2026-100714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100714 being exploited in the wild.
- How severe is CVE-2026-100714?
- Critical severity, with a CVSS score of 9.1, published 26 September 2026.
- Which products and versions are affected?
- Froxlor before 2.3.12, up to and including 2.3.10.
- Is there a fix for CVE-2026-100714?
- A patch was published on 2026-09-26: Fix released in version 2.3.12 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100714 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100714?
- Check whether you run Froxlor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The system.letsencryptchallengepath configuration setting is concatenated unescaped into an acme.sh command line executed by root cron via FileDir::safe_exec(). While safe_exec blacklists shell metacharacters (;|&><\$~?), it permits spaces and quotes, allowing word-splitting into arbitrary acme.sh arguments. An authenticated admin or API actor can inject options like --renew-hook, --pre-hook, --post-hook, or --config-home to achieve arbitrary command execution as root or write arbitrary files.
Affected products
- Froxlor Froxlor before 2.3.12, up to and including 2.3.10
Timeline
- 2026-09-26: disclosed: Public advisory published
- 2026-09-26: patched: Fix released in version 2.3.12