Revive Adserver: Cross-site request forgery in tracker invocation
Summary
A cross-site request forgery (CSRF) vulnerability in tracker-invocation.php in Revive Adserver 6.0.8 and earlier allows an attacker to change a tracker's name, description or advertiser assignment. A leftover state-changing handler accepts requests without checking a CSRF token, although the normal invocation-tag interface does not use it. Exploitation requires an authenticated user with the relevant permissions to visit an attacker-controlled page, so the impact is limited to integrity of ad-tracking metadata.
Affected
- Revive Adserver 6.0.8 and earlier (CNA range: 0 to 6.0.8)
- Earlier branches: Unknown.
Fixed in
- Revive Adserver 6.0.9 (per CNA; vendor release notes not yet verified)
Workaround
- Unknown. Interim measure: restrict access to the admin interface to management networks or VPN, and avoid using the admin session while browsing other sites.
Exploitation
- No evidence of exploitation in the wild found at time of writing.
- No public proof of concept found.
- Attack requires victim interaction and a logged-in user with relevant permissions.
Our recommendation
- Upgrade to Revive Adserver 6.0.9 as part of routine maintenance, after confirming the fix on the vendor's release page.
- Prioritise the upgrade for internet-facing instances with several admin accounts.
- Limit admin accounts and avoid using admin sessions while browsing other websites.
- Review tracker names, descriptions and advertiser assignments for unexpected changes.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- CVE Record (CNA HackerOne) www.cve.org
- HackerOne report hackerone.com
- VulDB vuldb.com
- OffSeq Radar radar.offseq.com
- Revive Adserver FAQ www.revive-adserver.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 21:15.
Original description (NVD)
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.
NVD references (1)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.