Quick answers
- Is CVE-2026-108560 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108560 being exploited in the wild.
- How severe is CVE-2026-108560?
- 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-108560?
- 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-108560 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108560?
- 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 reflected XSS vulnerability exists in updates-history.php where attacker-controlled values are inserted into XML command attributes without proper encoding, allowing injection of executable XHTML. An unauthenticated attack path exists because the session check incorrectly omits GET xajax requests, though authenticated administrators are also affected. The vulnerability is fixed in version 6.0.9 by enforcing session checks on both GET and POST requests and encoding XML attribute values in both response serializers.
Affected products
- Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed