Cross-Site Request Forgery

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

1. The HTML_Quickform library, as used in Revive Adserver before 3.2.2, allows remote attackers to bypass the CSRF protection mechanism via an empty token.CVE-2015-7364Revive-Adserver · 1.1% likely

   CWE-352

2. Multiple cross-site request forgery (CSRF) vulnerabilities in Revive Adserver before 3.2.2 allow remote attackers to hijack the authentication of users for requests that (1) perfo…CVE-2015-7366Revive-Adserver · 1.1% likely

   CWE-352

3. Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). A number of scripts in Revive Adserver's user interface are vulnerable to CSRF attacks: `www/admin/ban…CVE-2016-9455Revive-Adserver · 0.8% likely

   CWE-352

4. Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). The password recovery form in Revive Adserver is vulnerable to CSRF attacks. This vulnerability could…CVE-2016-9127Revive-Adserver · 0.8% likely

   CWE-352

5. Multiple cross-site request forgery (CSRF) vulnerabilities in Revive Adserver before 3.0.5 allow remote attackers to hijack the authentication of administrators for requests that…CVE-2014-9407Revive-Adserver · 0.6% likely

   CWE-352

6. Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). The Revive Adserver team conducted a security audit of the admin interface scripts in order to identif…CVE-2016-9456Revive-Adserver · 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.