Medium severity · published Mar 28, 2017
CVE-2016-9472
Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected XSS
5.4
CVSS
1.6%
EPSS
No
On KEV
Description
Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected XSS. The Revive Adserver web installer scripts were vulnerable to a reflected XSS attack via the dbHost, dbUser, and possibly other parameters. It has to be noted that the window for such attack vectors to be possible is extremely narrow and it is very unlikely that such an attack could be actually effective.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)1.6% · higher than 76% 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.4; 4.0.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-9472
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-9472
Permissions Required
https://github.com/revive-adserver/revive-adserver/commit/14ff73f0
Patch
https://github.com/revive-adserver/revive-adserver/commit/fcf72c8a
Permissions Required
https://hackerone.com/reports/170156
Patch
https://www.revive-adserver.com/security/revive-sa-2016-002/
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