Skip to main content
CVE-2026-107247VulnerabilityPublished

Revive Adserver · Authorization Bypass

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-107247· High 8.1

Not known to be exploited · CVSS 8.1 High · fixed in 6.0.9 : patch Adserver soon.

Data as of 11 Nov 2026, 19:47 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (hackerone)CVSS 3.08.1
Patch
Available – fixed in 6.0.9
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ReviveAdserverAffected
  • >=6.0.0 <=6.0.8
Fixed in–

AI-suggested

Upgrade Revive Adserver to version 6.0.9 or later, where the vulnerability is fixed by restoring POST parameter precedence in global input registration. No other mitigation is indicated or required once the patch is applied.

Description

Revive Adserver versions 6.0.0 through 6.0.8 contain an authorization bypass vulnerability that allows an authenticated manager restricted to one agency to access or modify resources of another agency. This occurs due to global input registration prioritizing GET parameters over POST parameters, conflicting with administration forms that use POST. An attacker can supply differing object identifiers in GET and POST requests to bypass permission checks, enabling unauthorized cross-agency changes, campaign ownership reassignment, and disclosure of campaign and banner data. The issue was introduced in a specific commit and fixed in version 6.0.9 by restoring POST parameter precedence.

References

Community reviews

Loading reviews…