Quick answers
- Is CVE-2026-50739 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50739 being exploited in the wild.
- How severe is CVE-2026-50739?
- 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-50739?
- 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-50739 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50739?
- 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 Revive Adserver 6.0.7 and earlier due to missing ownership validation in the `tracker-campaigns.php` script. While a previous fix (CVE-2026-34913) addressed ownership checks for certain operations, the reverse operation of linking trackers to campaigns remained unprotected. A remote attacker with low-level authenticated access can exploit this by submitting requests that associate their own trackers with campaigns belonging to different managers on the same instance. This results in unauthorized modification of campaign-tracker relationships and inconsistent data ownership within the database.
Affected products
- Revive Adserver 6.0.7 and earlier
Timeline
- 2026-06-26: disclosed: NVD publication date