CVE•Published 2017-03-28•Modified 2026-05-13•0 articles on news•6 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

—

Weaknesses (CWE)

CWE-75Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)

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

NVD MITRE Exploit-DB GitHub PoC trickest/cve VulnCheck

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).

Shodan · vuln tag0 hosts

vuln:CVE-2016-9471

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Revive-adserver Revive Adserver"

All exposed Revive-adserver Revive Adserver instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Revive Adserver"

HTTP body or banner mentions "Revive Adserver" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2016-9471