# CVE-2026-77168: Revive Adserver CSRF in tracker modification

Source: https://junglewise.ai/threats/cve-2026-77168-a-cross-site-request-forgery-vulnerability-in-tracker-invocation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

CVE-2026-77168 · Severity: medium · CVSS 4.3 · Published 2026-11-11

Revive Adserver is an ad management platform. A cross-site request forgery vulnerability in versions 6.0.8 and earlier allows an attacker to trick an authenticated administrator into modifying ad tracker settings (name, description, or advertiser assignment) without their knowledge. The attacker must craft a malicious webpage that the administrator visits while logged in, and the victim must interact with it.

Technologies: [Revive Adserver](https://junglewise.ai/threats/technologies/revive-adserver-1). Vendors: [Revive](https://junglewise.ai/threats/vendors/revive).

## Quick answers

**Is CVE-2026-77168 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-77168 being exploited in the wild.

**How severe is CVE-2026-77168?** Medium severity, with a CVSS score of 4.3, published 11 November 2026.

**Which products and versions are affected?** Revive Adserver 6.0.8 and earlier.

**Is there a fix for CVE-2026-77168?** Yes: fixed in Revive Adserver 6.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-77168 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-77168?** Check whether you run Revive Adserver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Revive Adserver 6.0.9

## Technical details

A leftover, unused state-changing handler in tracker-invocation.php accepts request parameters without CSRF token validation. An attacker can exploit this via a crafted cross-site request that executes with the victim's authenticated session credentials. The vulnerability requires victim interaction and an authenticated session; the unused handler was removed in version 6.0.9.

## Affected products

- Revive Adserver 6.0.8 and earlier

## Timeline

- 2026-11-11: disclosed
- 2026-11-11: patched: Fixed in version 6.0.9

## References

- [https://hackerone.com/reports/3981932](https://hackerone.com/reports/3981932)

## Related threats

- [Revive Adserver authorization bypass in channel-edit.php](https://junglewise.ai/threats/cve-2026-82978-an-authorization-bypass-in-channel-edit-php-in-revive-adserver-6)
- [Revive Adserver authorization bypass in campaign-zone linking](https://junglewise.ai/threats/cve-2026-68486-an-authorization-bypass-in-campaign-zone-linking-in-revive)
- [Revive Adserver authorization bypass in website listing](https://junglewise.ai/threats/cve-2026-68485-an-authorization-bypass-in-website-index-php-in-revive-adserver-6)
- [Revive Adserver reflected cross-site scripting in popup options](https://junglewise.ai/threats/cve-2026-108565-a-reflected-cross-site-scripting-vulnerability-in-the-popup)
- [Revive Adserver reflected XSS in invocation-tag generation](https://junglewise.ai/threats/cve-2026-108564-a-reflected-cross-site-scripting-vulnerability-in-the-invocation)