PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-50739 Revive CVE debrief

CVE-2026-50739 is a MEDIUM severity vulnerability in Revive Adserver 6.0.7 and earlier. The issue is a bypass for CVE-2026-34913, which allows low-privileged users to link their trackers to campaigns owned by other managers on the same instance. This leads to inconsistent ownership relationships. The vulnerability has a CVSS score of 4.3 and was published on 2026-06-26. The CVE record was last modified on 2026-06-29. The vulnerability is tracked by CVE.org and detailed in the NVD database.

Vendor
Revive
Product
Adserver
CVSS
MEDIUM 4.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-26
Original CVE updated
2026-06-29
Advisory published
2026-06-26
Advisory updated
2026-06-29

Who should care

Defenders of Revive Adserver instances should be aware of this vulnerability, as it allows low-privileged users to manipulate campaign and tracker ownership. This could lead to unauthorized access or modifications to sensitive data. Users of Revive Adserver 6.0.7 and earlier should review their instances for potential exploitation.

Technical summary

The vulnerability exists in the `tracker-campaigns.php` script of Revive Adserver 6.0.7 and earlier. A low-privileged user can exploit this bypass of CVE-2026-34913 to link their trackers to campaigns owned by other managers. The vulnerability has a CVSS vector of CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, indicating a Medium severity level. The CWE associated with this vulnerability is CWE-284.

Defensive priority

Defenders should prioritize patching Revive Adserver instances to version 6.0.8 or later. In the absence of a patch, defenders should monitor for suspicious activity related to tracker and campaign linking.

Recommended defensive actions

  • Patch Revive Adserver to version 6.0.8 or later.
  • Monitor for suspicious activity related to tracker and campaign linking.
  • Review and adjust user privileges to prevent low-privileged users from manipulating ownership relationships.
  • Implement additional logging and monitoring to detect potential exploitation attempts.
  • Consider compensating controls, such as Web Application Firewalls (WAFs), to detect and prevent exploitation.

Evidence notes

The CVE record and NVD detail provide official information about the vulnerability. The HackerOne report provides additional context and potential mitigation strategies. The vulnerability is considered Medium severity, with a CVSS score of 4.3.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-50739 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-50739

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-50739 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-50739

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.