phpMyFAQ 在 4.1.8 之前版本中存在一个认证绕过漏洞,影响其双因素认证(TOTP)的禁用功能。 处理器(可通过 POST 访问)仅验证用户是否已登录以及是否提供了有效的 CSRF token,随后即可禁用 TOTP,而不要求重新输入密码或当前的 TOTP 验证码。同样的降级操作也可以通过 PUT 内联实现,该接口在相同的“会话 + CSRF”防护下,接受一个普通的 表单字段。 攻击者若能劫持某个用户的会话,就可以悄无声息地移除任何账户(包括管理员账户)的双因素保护。一旦双因素保护被移除,仅凭密码即可成功
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-85591 | 7.1 HIGH | phpMyFAQ before 4.1.8 Authentication Bypass via Unverified Password Change |
| CVE-2026-85586 | 6.9 MEDIUM | phpMyFAQ before 4.1.8 CAPTCHA Bypass via store parameter |
| CVE-2026-85593 | 5.4 MEDIUM | phpMyFAQ before 4.1.8 Stored XSS via html_entity_decode |
| CVE-2026-85587 | 5.3 MEDIUM | phpMyFAQ before 4.1.8 Incorrect Authorization via Admin Pages |
| CVE-2026-85588 | 5.3 MEDIUM | phpMyFAQ before 4.1.8 TOTP Secret Exposure via Data Export |
| CVE-2026-85589 | 5.3 MEDIUM | phpMyFAQ before 4.2.0-alpha.2 Missing Authorization via Dashboard API |
| CVE-2026-85592 | 3.7 LOW | phpMyFAQ before 4.1.8 Authorization Bypass via question/create |
No comments yet