CVE-2026-108560 · Package
NO FIX YET · SEE WHAT TO DO
Revive Adserver's updates-history.php reflects attacker-supplied values into XML output without encoding, a reflected cross-site scripting flaw. A victim who opens a crafted link lets an attacker run JavaScript in their browser session.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Revive Adserver installations at version 6.0.8 or earlier. The unauthenticated path is a GET request to updates-history.php that skips the session check, so any reachable instance is exposed to a crafted link; administrator requests reach the same unsafe output.
Not affected if managed-hosting, version-6.0.9-or-later
Who cares php, revive-adserver, self-hosted
6.0.8 and earlier are affectedupdates-history.php is reachable from the internet on your ad server6.0.9A reflected cross-site scripting vulnerability in updates-history.php in Revive Adserver 6.0.8 and earlier allows an unauthenticated attacker to execute JavaScript in a victim's browser by persuading them to visit a crafted URL. Attacker-controlled values are included in XML command attributes without appropriate encoding, allowing injection of executable XHTML into the response. The preliminary session check omits GET xajax requests, exposing an unauthenticated attack path, while authenticated administrator requests also reach the unsafe output. The issue is fixed in Revive Adserver 6.0.9 by applying the session check to both GET and POST requests and encoding XML command attribute values in both response serializers.
This page as .md · .json · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.