Froxlor(版本 2.3.10 及之前)存在一个严重的安全漏洞。当未认证用户触发对 2FA 管理页面(例如 )的 GET 请求时,系统会立即禁用该用户的两步验证(2FA)功能,过程中没有进行任何确认、重新认证或 CSRF 令牌验证。 尽管系统全局启用了 CSRF 中间件,但它仅覆盖 POST/PUT/PATCH/DELETE 请求。此外,会话 cookie 被设置为 ,因此跨站顶级导航(如点击链接或重定向)会携带受害者的会话信息,并静默清除 和 相关数据。此漏洞同时影响客户和管理员的 2FA 处理程序。 攻击者
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.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| 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-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-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 |
No comments yet