Quick answers
- Is CVE-2026-108561 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108561 being exploited in the wild.
- How severe is CVE-2026-108561?
- 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-108561?
- Yes: fixed in 6.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108561 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108561?
- 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: 6.0.9
Technical details
A stored XSS vulnerability exists in the report date-selection controls where the period_preset parameter is saved to the session and inserted into JavaScript without proper JSON encoding. An unauthenticated attacker can craft a malicious URL that, when visited by a victim who completes normal reauthentication, stores an attacker-controlled payload that executes on initial and subsequent report views. The vulnerability is fixed in version 6.0.9 through appropriate JSON encoding of date-selection values in the JavaScript context.
Affected products
- Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed