Quick answers
- Is CVE-2026-44961 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44961 being exploited in the wild.
- How severe is CVE-2026-44961?
- Informational severity, with a CVSS score of 0, published 23 June 2026.
- Which products and versions are affected?
- Revive-Adserver Adserver <= 6.0.6.
- Is there a fix for CVE-2026-44961?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44961 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-44961?
- Check whether you run Revive-Adserver 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.
Technical details
A validation bypass exists in the addUser method of the XML-RPC API in Revive Adserver versions 6.0.6 and earlier. This flaw was introduced as a regression in a previous security fix (CVE-2025-55129). The vulnerability allows an attacker with API access to bypass input sanitization when creating new users, enabling the injection of payloads for stored Cross-Site Scripting (XSS) or the creation of usernames that mimic existing accounts for impersonation. The issue is classified under CWE-287 (Improper Authentication) and has been addressed by adding proper validation to the affected method.
Affected products
- Revive Adserver <= 6.0.6
Timeline
- 2026-06-23: disclosed
- 2026-06-23: advisory