Authorization bypass in Revive Adserver allows cross-agency changes
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
Revive Adserver 6.0.0 through 6.0.8 contains an authorization bypass. Global input registration gives GET parameters precedence over POST parameters, so permission checks and later operations can target different objects than the ones the user is authorized for (CWE-639). An authenticated manager restricted to one agency can exploit this to change resources of another agency, reassign campaign ownership, and read campaign and banner data.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Description from the CNA
An authorization bypass in Revive Adserver 6.0.0 through 6.0.8 allows an authenticated manager restricted to one agency to access or modify resources belonging to another agency. Global input registration gives GET parameters precedence over POST parameters, while submitted administration forms use POST values. By supplying authorized object identifiers in the query string and different identifiers in the POST body, an attacker can cause permission checks and subsequent operations to target different objects. This permits unauthorized cross-agency changes, campaign ownership reassignment and disclosure of campaign and banner data. The regression was introduced in commit 156dee7bc3283c128f35e5a31bb305054cc8de1b and is fixed in Revive Adserver 6.0.9 by restoring POST precedence in global input registration.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Revive | Adserver | 6.0.0 – 6.0.8 | — | No fix listed | CNA |
- Adserver VendorRevive Affected 6.0.0 – 6.0.8 Fixed in — No fix listed CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:* | — | — | Revive Adserver |
- cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:* Versions — — ·Revive Adserver
Remediation
Upgrade Revive Adserver to version 6.0.9, which restores POST precedence in global input registration.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Timeline
- 2026-11-11 Threatist record created from CVE-2026-107247
- 2026-11-11 Alias added: GHSA-h452-8c52-gq69
References
More Revive vulnerabilities
- TI-2025-31114 Improper access control in Revive Adserver CVSS 3.0HIGH 8.8
- TI-2025-34810 Cross-site scripting in Revive Adserver CVSS 3.0MEDIUM 6.5
- TI-2022-04278 Revive Old Posts – Social Media Auto Post and Scheduling Plugin < 9.0.11 - PHP Object Injection CVSS 3.1HIGH 7.2
- TI-2023-11756 The login page of Revive Adserver v5.4.1 is vulnerable to brute force attacks. CVSS 3.1HIGH 7.5
- TI-2025-34812 Uncontrolled resource consumption in Revive Adserver CVSS 3.0MEDIUM 6.5
- TI-2025-32749 Missing authorization in Revive Adserver CVSS 3.1MEDIUM 6.5
Sources
- CVE-2026-107247 · CVE Program
- CVE-2026-107247 · NVD
- FIRST EPSS
- GHSA-h452-8c52-gq69 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences