Filtered by vendor Phpmyfaq
Subscribe
Search
Total
14 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2023-0790 | 1 Phpmyfaq | 1 Phpmyfaq | 2023-12-18 | N/A | 8.8 HIGH |
| Uncaught Exception in GitHub repository thorsten/phpmyfaq prior to 3.1.11. | |||||
| CVE-2023-0793 | 1 Phpmyfaq | 1 Phpmyfaq | 2023-12-18 | N/A | 8.8 HIGH |
| Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.11. | |||||
| CVE-2018-16651 | 1 Phpmyfaq | 1 Phpmyfaq | 2020-08-24 | 9.0 HIGH | 7.2 HIGH |
| The admin backend in phpMyFAQ before 2.9.11 allows CSV injection in reports. | |||||
| CVE-2017-15730 | 1 Phpmyfaq | 1 Phpmyfaq | 2019-03-14 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php. | |||||
| CVE-2018-16650 | 1 Phpmyfaq | 1 Phpmyfaq | 2018-11-02 | 6.8 MEDIUM | 8.8 HIGH |
| phpMyFAQ before 2.9.11 allows CSRF. | |||||
| CVE-2014-6046 | 1 Phpmyfaq | 1 Phpmyfaq | 2018-11-01 | 6.8 MEDIUM | 8.8 HIGH |
| 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. | |||||
| CVE-2014-6045 | 1 Phpmyfaq | 1 Phpmyfaq | 2018-10-31 | 6.5 MEDIUM | 7.2 HIGH |
| SQL injection vulnerability in phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors involving the restore function. | |||||
| CVE-2017-15808 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-25 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php. | |||||
| CVE-2017-15729 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for adding a glossary. | |||||
| CVE-2017-15734 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php. | |||||
| CVE-2017-15732 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/news.php. | |||||
| CVE-2017-15731 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.adminlog.php. | |||||
| CVE-2017-15733 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/ajax.attachment.php and admin/att.main.php. | |||||
| CVE-2017-15735 | 1 Phpmyfaq | 1 Phpmyfaq | 2017-10-24 | 6.8 MEDIUM | 8.8 HIGH |
| In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary. | |||||