Quick answers
- Is CVE-2026-108558 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108558 being exploited in the wild.
- How severe is CVE-2026-108558?
- Medium severity, with a CVSS score of 6.1, published 11 November 2026.
- Which products and versions are affected?
- Revive Adserver 6.0.8 and earlier.
- Is there a fix for CVE-2026-108558?
- Yes: fixed in Revive Adserver 6.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108558 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-108558?
- Check whether you run Revive Adserver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Revive Adserver 6.0.9
Technical details
A reflected XSS vulnerability exists in the conversion-statistics pages where an incorrect ownership check validates the advertiser identifier instead of the website identifier, allowing malicious input to reach HTML output without proper encoding. A related output encoding issue affects the hour parameter. An unauthenticated attacker can craft a malicious URL and persuade an authenticated user to visit it, causing arbitrary JavaScript execution in the user's browser context. The vulnerability is patched in version 6.0.9 by implementing correct website identifier validation and normalizing the hour parameter before output.
Affected products
- Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed