Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-100714— Froxlor before 2.3.12 Command Injection via letsencryptchallengepath

Quick assessment

Affected
froxlor froxlor
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Froxlor 2.3.12 之前的版本未对 配置项进行限制或转义处理。与 GHSA-33mp 中被加固的同类配置不同,该字段缺乏 正则表达式校验或 令牌保护机制。其值在 中被未转义地拼接至 命令行,并通过 以 root 权限由 cron 定时任务执行。 由于 仅对分号(;)、管道符( 受影响版本为 2.3.10 及更早版本;该问题已在 2.3.12 版本中修复。

CVSS 9.1 · Critical EPSS 0.55% · P44

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-100714

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Froxlor before 2.3.12 Command Injection via letsencryptchallengepath
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
参数注入或修改
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
froxlor froxlor 0 ~ 2.3.12 -

II. Public POCs for CVE-2026-100714

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-100714

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-100714 (1)

Other References for CVE-2026-100714 (1)

Same Patch Batch · froxlor · 2026-09-26 · 13 CVEs total

CVE-2026-100717 9.9 CRITICAL froxlor before 2.3.12 CRLF Injection via validateUrl userinfo
CVE-2026-100716 9.9 CRITICAL Froxlor before 2.3.12 Privilege Escalation via Symlink
CVE-2026-100715 9.6 CRITICAL Froxlor before 2.3.12 Arbitrary File Deletion via Symlink
CVE-2026-100720 8.7 HIGH Froxlor before 2.3.12 Stored XSS via SSL certificate issuer
CVE-2026-100713 7.8 HIGH Froxlor before 2.3.12 Privilege Escalation via SSH Key Sync
CVE-2026-100711 7.5 HIGH froxlor before 2.3.12 Authentication Bypass via Session Persistence
CVE-2026-100709 7.5 HIGH Froxlor before 2.3.12 2FA Bypass via Namespace Confusion
CVE-2026-100718 7.1 HIGH Froxlor before 2.3.12 Authentication Bypass via EmailSender.add
CVE-2026-100708 7.1 HIGH Froxlor before 2.3.13 Private Key Disclosure via Certificates API
CVE-2026-100712 6.5 MEDIUM froxlor before 2.3.12 Two-Factor Authentication Bypass via CSRF
CVE-2026-100719 6.5 MEDIUM Froxlor before 2.3.12 Credential Disclosure via DirProtections API
CVE-2026-100710 4.9 MEDIUM Froxlor before 2.3.12 DKIM Private Key Disclosure via API

IV. Related Vulnerabilities

V. Comments for CVE-2026-100714

No comments yet


Leave a comment