Skip to main content
CVE-2026-108565VulnerabilityPublished

Reflected Cross-site Scripting Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-108565· Medium 4.7

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

Data as of 11 Nov 2026, 19:39 UTC

CVSS 3.0 base score
4.7Medium
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.04.7
Patch
Available – fixed in 6.0.9
CVSS:3.0/AV:N/AC:H/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 to Revive Adserver version 6.0.9 or later, where the vulnerability is fixed by applying HTML encoding to the affected popup option parameters. No other mitigation is specified or required as the fix addresses the root cause.

Description

A reflected cross-site scripting (XSS) vulnerability exists in the popup invocation options of Revive Adserver version 6.0.8 and earlier. This flaw allows an unauthenticated attacker to execute arbitrary JavaScript in the browser of an authenticated user by tricking them into visiting a specially crafted URL. The vulnerability arises because certain request parameters (top, left, timeout, delay) are inserted into HTML attributes without proper encoding. Exploitation requires the presence of an existing popup zone, which can only be created through the administrator API and is not available via the standard zone-creation interface. The issue is resolved in version 6.0.9 by applying HTML encoding to the affected parameters.

References

Community reviews

Loading reviews…