CVE-2026-77168: CSRF
A cross-site request forgery vulnerability in tracker-invocation.php in Revive Adserver 6.0.8 and earlier allows an attacker to modify a tracker's name, description or advertiser assignment using an authenticated victim's permissions. A leftover state-changing handler accepts request parameters without verifying a CSRF token, although it is not used by the normal invocation-tag interface. Exploitation requires victim interaction and a request path that carries the victim's session credentials. The issue is fixed in Revive Adserver 6.0.9 by removing the unused tracker-modification handler.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Revive Adserverto a version that resolves this vulnerability.Fixed in 6.0.9
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users authenticated to a Revive Adserver instance running version 6.0.8 or earlier may be exposed if an attacker can cause their browser to send a crafted request with that user's session credentials. The resulting changes are limited by the authenticated victim's tracker-management permissions.
Does normal use of the invocation-tag interface trigger the vulnerable handler?
No. The affected tracker-modification handler is described as leftover functionality and is not used by the normal invocation-tag interface.
What can an attacker change through successful exploitation?
An attacker can modify a tracker's name, description, or advertiser assignment using the permissions of the authenticated victim.
What should organizations do if they cannot patch immediately?
The provided information identifies removal of the unused tracker-modification handler as the fix in version 6.0.9. No specific temporary mitigation is provided.