Skip to main content
CVE-2026-108560VulnerabilityPublished

updates-history.php · Reflected Cross-site Scripting Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-108560· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium · fixed in 6.0.9 : update Adserver when convenient.

Data as of 11 Nov 2026, 19:39 UTC

CVSS 3.0 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (hackerone)CVSS 3.06.1
Patch
Available – fixed in 6.0.9
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ReviveAdserverAffected
  • <=6.0.8
Fixed in–

AI-suggested

Upgrade Revive Adserver to version 6.0.9 or later, where the vulnerability is fixed by applying session checks to both GET and POST requests and encoding XML command attribute values in response serializers. No other mitigation is required as the fix addresses the root cause.

Description

A reflected cross-site scripting (XSS) vulnerability exists in updates-history.php in Revive Adserver versions 6.0.8 and earlier. This flaw allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser by tricking them into visiting a specially crafted URL. The vulnerability arises because attacker-controlled input is included in XML command attributes without proper encoding. The session check does not cover GET xajax requests, enabling unauthenticated exploitation, and authenticated administrator requests are also affected. The issue is resolved in version 6.0.9 by extending session checks to both GET and POST requests and encoding XML command attribute values in response serializers.

References

Community reviews

Loading reviews…