CVE•Published 2017-03-28•Modified 2026-05-13•0 articles on news•5 live references•NVD data

CVE-2016-9471Revive-adserver · Revive_adserver

Vulnerability data via NVD (ingested)

CVSS v3.1
3.1
LOW
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
EPSS percentile
—
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.

Timeline
Published 2017-03-28
Modified 2026-05-13

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub (1)

We haven't classified any articles referencing CVE-2016-9471 yet. The external references above still apply.