Skip to main content
VulnerabilityPublished

CVE-2026-108558: 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 proper validation of the website identifier and normalization of the hour parameter. No other mitigation is indicated or necessary once patched.

Description

CVE-2026-108558 is a reflected cross-site scripting (XSS) vulnerability in Revive Adserver versions up to 6.0.8. It affects the conversion-statistics pages where an unauthenticated attacker can execute JavaScript in an authenticated user's browser by tricking them into visiting a crafted URL. The flaw arises from an incorrect ownership check that validates the advertiser identifier instead of the website identifier, allowing malicious input to be rendered without proper encoding. The vulnerability also involves improper handling of the hour parameter. This issue is fixed in version 6.0.9 by correcting the identifier validation and normalizing the hour parameter.

References

Community reviews

Loading reviews…