Skip to content
Fencer Intel
low 3.1

CVE-2016-9471 json

Revive Adserver before 3.2.5 and 4.0.0 suffers from Special Element Injection.

published 2017-03-28 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10277

cvss
3.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

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.

Patch / fix

Exploit prediction

1.37% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 3.1 CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
NVD 2.0 2.1 AV:N/AC:H/Au:S/C:N/I:P/A:N

Affected products

  • n/a Revive Adserver All versions before 3.2.5 and 4.0.0

Classification

Weakness
  • CWE-75 Failure to Sanitize Special Elements into a Different Plane

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.