Quick answers
- Is CVE-2026-50744 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50744 being exploited in the wild.
- How severe is CVE-2026-50744?
- Medium severity, with a CVSS score of 4.3, published 26 June 2026.
- Which products and versions are affected?
- Revive-Adserver Adserver 6.0.7 and earlier.
- Is there a fix for CVE-2026-50744?
- 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-50744 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50744?
- 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
An improper access control vulnerability exists in the XML-RPC API of Revive Adserver version 6.0.7 and earlier. The root cause is found in the 'ox.login' method, which fails to invalidate session identifiers when an authentication attempt fails or encounters an error. While the API correctly returns an error message, it simultaneously issues a valid session ID cookie in the HTTP response headers. A remote attacker with basic credentials can capture this leaked session ID to authenticate as an administrator and perform subsequent API calls without further restriction. This vulnerability is tracked as CWE-284.
Affected products
- Revive Adserver 6.0.7 and earlier
Timeline
- 2026-06-26: advisory: NVD publication date