Skip to main content
CVE-2026-108558VulnerabilityPublished

Reflected Cross-site Scripting Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-108558· 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:47 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 mitigations are indicated or required once the patch is applied.

Description

A reflected cross-site scripting (XSS) vulnerability exists in the conversion-statistics pages 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 root cause is an incorrect ownership check that validates the advertiser identifier instead of the website identifier, leading to malicious input being rendered without proper encoding. Additionally, the hour parameter is improperly handled. The vulnerability is fixed in version 6.0.9 by correcting the identifier validation and normalizing the hour parameter.

References

Community reviews

Loading reviews…