VulnerabilityPublished 11 Nov 2026

CVE-2026-68485: Revive Adserver · Insecure Direct Object Reference

Affects Revive AdserverSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium · fixed in 6.0.9 : update Revive Adserver when convenient.

Data as of 11 Nov 2026, 18:02 UTC

CVSS 3.0 base score

4.3Medium

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.0	4.3

Patch: Available – fixed in 6.0.9

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ReviveAdserver	Affected <=6.0.8	Fixed in–

AI-suggested

Upgrade Revive Adserver to version 6.0.9 or later, where the vulnerability is fixed by obtaining the agency identifier from the authenticated account rather than the request parameter. No other mitigation is required as the issue is resolved in this official fix.

Description

CVE-2026-68485 is an authorization bypass vulnerability in Revive Adserver versions 6.0.8 and earlier. It allows an authenticated manager restricted to one agency to view another agency's website listing by modifying the agencyid request parameter. The disclosed information includes website names, identifiers, and timestamps. Ownership checks remain enforced on detailed website pages. The issue is fixed in version 6.0.9 by deriving the agency identifier from the authenticated account rather than the request.

Impact

An authenticated manager restricted to a single agency can view website listings of other agencies, leading to unauthorized disclosure of website metadata including names, identifiers, and timestamps. There is no indication of data modification or broader access beyond this information disclosure. The impact is limited to confidentiality loss of some agency website listings.

Summary

This vulnerability (CWE-639) in Revive Adserver affects the website-index.php component, where an authenticated user with limited agency access can bypass authorization controls by manipulating the agencyid parameter in requests. This leads to unauthorized disclosure of website listings belonging to other agencies, exposing metadata such as website names, IDs, and timestamps. The flaw does not allow modification or access to detailed website pages, which still enforce ownership verification. The vendor fixed this issue in version 6.0.9 by changing the source of the agency identifier to the authenticated user's account context instead of user-controlled input.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

hackerone.com/reports/3883840 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 18:02 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats