Quick answers
- Is CVE-2026-108562 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108562 being exploited in the wild.
- How severe is CVE-2026-108562?
- Medium severity, with a CVSS score of 5.4, published 11 November 2026.
- Which products and versions are affected?
- Revive-Adserver Revive Adserver 6.0.8 and earlier.
- Is there a fix for CVE-2026-108562?
- 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-108562 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-108562?
- Check whether you run Revive-Adserver 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 stored XSS vulnerability exists in maintenance-appendcode-check.php where tracker names are not properly HTML-encoded before display in maintenance results. An authenticated manager can store a malicious tracker name that executes arbitrary JavaScript in an administrator's browser when the maintenance page is accessed. The fix in version 6.0.9 applies HTML-encoding to tracker names during display.
Affected products
- Revive Adserver Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed