---
id: "CVE-2026-77168"
page: "https://infrastack.ai/live/CVE-2026-77168"
kind: "vulnerability"
aliases: ["CVE-2026-77168"]
title: "Revive Adserver: forged requests can change tracker names and advertiser assignments"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "php", "revive-adserver", "self-hosted"]
not_affected_if: ["managed-hosting", "version-6.0.9-or-later"]
published_at: "2026-11-11T18:19:49+00:00"
first_seen_at: "2026-11-11T18:28:43+00:00"
updated_at: "2026-11-11T18:29:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-77168", "first_seen_at": "2026-11-11T18:28:43+00:00"}]
exploit_sources: []
---

# Revive Adserver: forged requests can change tracker names and advertiser assignments

Link for people: https://infrastack.ai/live/CVE-2026-77168 (this .md is for agents)

A leftover handler in tracker-invocation.php accepts changes to a tracker's name, description or advertiser assignment without checking a CSRF token. An attacker who tricks a logged-in administrator into visiting a malicious page can make those changes using the victim's permissions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Revive Adserver version, for example by reading the version in the admin interface or the package metadata, and compare it with `6.0.9`.
- Look for `tracker-invocation.php` in the install and confirm whether the tracker-modification handler is present.

## Fix

- Revive Adserver: upgrade to `6.0.9`, which removes the unused tracker-modification handler.

## Timeline

- 2026-11-11T18:28:43+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-77168

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_