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 |
|---|
| CVE-2026-75918 | 8.8 HIGH | phpMyFAQ before 4.1.7 Authentication Bypass via Tracking File |
| CVE-2026-76208 | 8.2 HIGH | phpMyFAQ 3.1.0 through 4.1.6 Authentication Bypass via LDAP |
| CVE-2026-76207 | 8.1 HIGH | phpMyFAQ before 4.1.7 2FA Bypass via Remember-Me Cookie |
| CVE-2026-76213 | 7.4 HIGH | phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle |
| CVE-2026-76214 | 7.4 HIGH | phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge |
| CVE-2026-76210 | 6.5 MEDIUM | phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export |
| CVE-2026-75919 | 5.3 MEDIUM | phpMyFAQ before 4.1.7 Authentication Bypass via Setup API |
| CVE-2026-75920 | 5.3 MEDIUM | phpMyFAQ before 4.1.6 Information Disclosure via Backup ZIP |
| CVE-2026-76206 | 5.3 MEDIUM | phpMyFAQ before 4.1.7 Information Disclosure via PDF Export |
| CVE-2026-76215 | 5.3 MEDIUM | phpMyFAQ before 4.1.7 Missing Authorization via child resources |
| CVE-2026-76212 | 5.3 MEDIUM | phpMyFAQ before 4.1.7 LIKE Wildcard Injection via PostgreSQL |
| CVE-2026-76209 | 4.3 MEDIUM | phpMyFAQ before v4.1.6 Registration Bypass via API |
| CVE-2026-76211 | 4.3 MEDIUM | phpMyFAQ before 4.1.7 Information Disclosure via Admin API |
No comments yet