Cross-Site Request Forgery

Every one of the 11 is a mark on the map. Named now: 1 to 11, most at risk first.

1. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.ratings.php.CVE-2017-15730Phpmyfaq · 2.5% likely

   CWE-352

2. 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)…CVE-2014-6046Phpmyfaq · 1.9% likely

   CWE-352

3. In phpMyFaq before 2.9.9, there is CSRF in admin/ajax.config.php.CVE-2017-15808Phpmyfaq · 1.2% likely

   CWE-352

4. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for modifying a glossary.CVE-2017-15735Phpmyfaq · 1.1% likely

   CWE-352

5. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.main.php.CVE-2017-15734Phpmyfaq · 1.1% likely

   CWE-352

6. Cross-site request forgery (CSRF) vulnerability in phpMyFAQ before 2.8.6 allows remote attackers to hijack the authentication of arbitrary users for requests that modify settings.CVE-2014-0813Phpmyfaq · 1.1% likely

   CWE-352

7. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/stat.adminlog.php.CVE-2017-15731Phpmyfaq · 0.6% likely

   CWE-352

8. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) for adding a glossary.CVE-2017-15729Phpmyfaq · 0.6% likely

   CWE-352

9. 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-15733Phpmyfaq · 0.6% likely

   CWE-352

10. In phpMyFAQ before 2.9.9, there is Cross-Site Request Forgery (CSRF) in admin/news.php.CVE-2017-15732Phpmyfaq · 0.6% likely

    CWE-352

11. phpMyFAQ before 2.9.11 allows CSRF.CVE-2018-16650Phpmyfaq · 0.5% likely

    CWE-352

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.