CVE-2016-9471
Revive Adserver before 3.2.5 and 4.0.0 suffers from Special Element Injection.
Does this matter?
Lower severity and a low EPSS score (1.37%). Track it; it rarely justifies an emergency change on its own.
Description
Revive Adserver before 3.2.5 and 4.0.0 suffers from Special Element Injection. Usernames weren't properly sanitised when creating users on a Revive Adserver instance. Especially, control characters were not filtered, allowing apparently identical usernames to co-exist in the system, due to the fact that such characters are normally ignored when an HTML page is displayed in a browser. The issue could have therefore been exploited for user spoofing, although elevated privileges are required to create users within Revive Adserver.
- CVSS 3.0
- 3.1 LOWCVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
- EPSS
- 1.37% probability · 72th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-75
- Affected
- revive-adserver/revive adserver
- Source
- support@hackerone.com
EPSS 1.4% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://github.com/revive-adserver/revive-adserver/commit/05b1ecebPatch, Third Party Advisory
- https://hackerone.com/reports/128181Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-002/Patch, Vendor Advisory
- https://github.com/revive-adserver/revive-adserver/commit/05b1ecebPatch, Third Party Advisory
- https://hackerone.com/reports/128181Permissions Required
- https://www.revive-adserver.com/security/revive-sa-2016-002/Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.