phpMyFAQ 4.1.8 之前的版本在用户控制面板 API 端点中存在身份验证绕过漏洞,允许已认证的攻击者在未验证当前密码的情况下修改账户密码。拥有会话访问权限的攻击者可以通过向用户数据更新端点提交仅包含 CSRF 令牌的 PUT 请求,静默地更改任意用户(包括管理员)的密码,从而导致不可逆的账户接管和受害者被锁定。
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-85590 | 7.1 HIGH | phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable |
| 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