Vulnerabilities > Phpmyfaq > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2022-12-11 | CVE-2022-4407 | Cross-site Scripting vulnerability in PHPmyfaq Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.9. | 6.1 |
| 2022-12-11 | CVE-2022-4408 | Cross-site Scripting vulnerability in PHPmyfaq Cross-site Scripting (XSS) - Stored in GitHub repository thorsten/phpmyfaq prior to 3.1.9. | 5.4 |
| 2022-10-31 | CVE-2022-3765 | Cross-site Scripting vulnerability in PHPmyfaq Cross-site Scripting (XSS) - Stored in GitHub repository thorsten/phpmyfaq prior to 3.1.8. | 5.4 |
| 2022-10-31 | CVE-2022-3766 | Cross-site Scripting vulnerability in PHPmyfaq Cross-site Scripting (XSS) - Reflected in GitHub repository thorsten/phpmyfaq prior to 3.1.8. | 6.1 |
| 2018-09-07 | CVE-2018-16650 | Cross-Site Request Forgery (CSRF) vulnerability in PHPmyfaq phpMyFAQ before 2.9.11 allows CSRF. | 6.8 |
| 2018-08-28 | CVE-2014-6050 | 7PK - Security Features vulnerability in PHPmyfaq phpMyFAQ before 2.8.13 allows remote attackers to bypass the CAPTCHA protection mechanism by replaying the request. | 5.0 |
| 2018-08-28 | CVE-2014-6049 | Improper Authorization vulnerability in PHPmyfaq phpMyFAQ before 2.8.13 allows remote authenticated users with admin privileges to bypass authorization via a crafted instance ID parameter. | 5.5 |
| 2018-08-28 | CVE-2014-6048 | Information Exposure vulnerability in PHPmyfaq phpMyFAQ before 2.8.13 allows remote attackers to read arbitrary attachments via a direct request. | 5.0 |
| 2018-08-28 | CVE-2014-6047 | Permission Issues vulnerability in PHPmyfaq phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to read arbitrary attachments by leveraging incorrect "download an attachment" permission checks. | 5.0 |
| 2018-08-28 | CVE-2014-6046 | Cross-Site Request Forgery (CSRF) vulnerability in PHPmyfaq Multiple cross-site request forgery (CSRF) vulnerabilities in phpMyFAQ before 2.8.13 allow remote attackers to hijack the authentication of unspecified users for requests that (1) delete active users by leveraging improper validation of CSRF tokens or that (2) delete open questions, (3) activate users, (4) publish FAQs, (5) add or delete Glossary, (6) add or delete FAQ news, or (7) add or delete comments or add votes by leveraging lack of a CSRF token. | 6.8 |