Quick answers
- Is CVE-2026-107662 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107662 being exploited in the wild.
- How severe is CVE-2026-107662?
- High severity, with a CVSS score of 8.8, published 11 November 2026.
- Which products and versions are affected?
- Revive Adserver 6.0.8 and earlier.
- Is there a fix for CVE-2026-107662?
- 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-107662 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-107662?
- 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
The vulnerability stems from inconsistent handling of request input precedence between permission checks and database queries in banner-zone.php and campaign-zone.php. An attacker with restricted manager access can pass validation with an authorized numeric identifier while injecting a different, attacker-controlled value into the SQL query, enabling blind SQL injection to extract arbitrary database values. Fixes require two commits (e301dbbb7 and 0aa9d0124) that enforce consistent POST-before-GET precedence and exclude cookies from input helpers.
Affected products
- Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed