High severity · published Mar 28, 2017
CVE-2016-9455
Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF)
8.8
CVSS
0.8%
EPSS
No
On KEV
Description
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/banner-acl.php`, `www/admin/banner-activate.php`, `www/admin/banner-advanced.php`, `www/admin/banner-modify.php`, `www/admin/banner-swf.php`, `www/admin/banner-zone.php`, `www/admin/tracker-modify.php`.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.8% · higher than 56% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
RA
Revive Adserver · Revive-adserver
through 3.2.2 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-9455
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-9455
www.securityfocus.com
http://www.securityfocus.com/bid/83964
Issue Tracking
https://github.com/revive-adserver/revive-adserver/commit/65a9c8119b4bc7493fd957e1a8d6f6f731298b45
Permissions Required
https://hackerone.com/reports/97123
Patch
https://www.revive-adserver.com/security/revive-sa-2016-001/
More from Revive Adserver
9.8
CVE-2016-9125
Revive Adserver before 3.2.3 suffers from session fixation, by allowing arbitrary session identifiers to be forced and, at the same time, by not invalidating the existing session…
9.8
CVE-2016-9124
Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts
9.8
CVE-2017-5830
Revive Adserver before 4.0.1 allows remote attackers to execute arbitrary code via serialized data in the cookies related to the delivery scripts
9.0
CVE-2016-9470
Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected File Download
8.8
CVE-2026-50741
Bypass to the fix for CVE-2026-34916