Skip to main content
VulnerabilityPublished

CVE-2026-108561: Revive Adserver · Cross-site Scripting

Affects Revive AdserverSource CVE Database V5

0
Compare

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

Data as of 11 Nov 2026, 18:04 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 JSON encoding to date-selection values in the JavaScript context. No other mitigations are indicated by the vendor advisory. Users should ensure they are not running affected versions (<=6.0.8).

Description

CVE-2026-108561 is a stored cross-site scripting (XSS) vulnerability in Revive Adserver versions 6.0.8 and earlier. It affects the report date-selection controls, allowing an unauthenticated attacker to execute arbitrary JavaScript in a victim's browser by tricking them into visiting a crafted report URL and completing reauthentication. The vulnerability arises from improper encoding of an attacker-controlled period_preset value stored in the victim's session and inserted into JavaScript. This issue is fixed in version 6.0.9 by applying appropriate JSON encoding to date-selection values.

References

Community reviews

Loading reviews…