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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-100716— Froxlor before 2.3.12 Privilege Escalation via Symlink

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.10 及更早版本中,客户数据导出(DataDump)定时任务未能对导出目标路径的中间路径组件进行有效验证: 在遍历路径组件时存在一个“差一”(off-by-one)错误,导致跳过了客户主目录下的首个路径段;而 中的防护措施仅使用 检查了最终路径组件。若一个已认证的客户账户启用了导出功能,该用户可将导出目的地设置为自身网络空间内的真实子目录,随后在受权限保护的 root 用户定时任务执行前,将某个中间路径组件替换为符号链接。定时任务中使用的 命令会递归地将该符号链接所

CVSS 9.9 · Critical EPSS 0.39% · P31
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-100716

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 Privilege Escalation via Symlink
Source: CVE Program / CVE List V5
Vulnerability Description
Froxlor is a server administration panel. In versions 2.3.10 and earlier, the customer data-export (DataDump) cron fails to validate intermediate path components of the export destination: Froxlor\FileDir::makeCorrectDir() contains an off-by-one in its path-component walk that skips the first segment below the customer home directory, and the guard in ExportCron.php checks only the final component with is_link(). An authenticated customer whose account has the export feature enabled can schedule an export into a genuine subdirectory of their own webspace, then replace an intermediate path component with a symlink before the root-owned cron runs. The cron's `chown -R` then recursively changes ownership of the linked directory tree — for example /etc — to the customer's UID, yielding host root and cross-tenant compromise. Exploitation is deterministic and requires no race. This is an incomplete fix of GHSA-75h4-... The issue is fixed in Froxlor 2.3.12.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/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-100716

# 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-100716

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

Vendor Advisories for CVE-2026-100716 (1)

Other References for CVE-2026-100716 (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-100715 9.6 CRITICAL Froxlor before 2.3.12 Arbitrary File Deletion via Symlink
CVE-2026-100714 9.1 CRITICAL Froxlor before 2.3.12 Command Injection via letsencryptchallengepath
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-100716

No comments yet


Leave a comment