Skip to main content

Revive Adserver CVE-2026-50741

| EUVDEUVD-2026-39602 HIGH
Code Injection (CWE-94)
2026-06-26 hackerone GHSA-66rh-2cvm-487w
8.8
CVSS 3.0 · Vendor: hackerone
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege account
  2. Delivery
    Submit disallowed-but-valid plugin `type` or call ox.setChannelTargeting XML-RPC
  3. Exploit
    Bypass CVE-2026-34916 allowlist
  4. Execution
    Inject code into plugin loader
  5. Persist
    Execute arbitrary code on server
  6. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated low-privilege account (CVSS PR:L) and network reachability to the Revive Adserver application; no user interaction is needed. The concrete trigger is one of two named paths: supplying a disallowed-yet-structurally-valid plugin identifier in the type parameter, or calling the ox.setChannelTargeting XML-RPC API method - so an instance with the XML-RPC interface disabled removes that second vector. The principal limiting factor is the credential requirement: the attacker must first hold a valid (even minimally privileged) account, so instances that restrict account creation and are not internet-exposed face materially lower risk.

Impact

The CVSS 3.0 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) describes a network-reachable, low-complexity attack that requires only low-privilege authentication and no user interaction, with full triple-impact - a genuinely high-priority profile for any internet-exposed instance. No EPSS score, KEV entry, or confirmed public POC was provided, so there is no signal of active or widespread exploitation; the realistic risk is therefore driven by the low bar to exploit once an attacker holds any authenticated account. A notable nuance: this is explicitly a bypass of a previously shipped fix, and multiple independent researchers reported equivalent vectors, which raises the likelihood that further variants or working exploit code surface quickly even though none is confirmed now. Treat the PR:L requirement as the main limiting factor - exposure depends on how easily an attacker can obtain a low-privilege Revive account.

Exploit ScenarioDerived

An attacker who has obtained any low-privilege Revive Adserver account sends a crafted request specifying a disallowed-but-valid plugin identifier as the type value, or invokes the ox.setChannelTargeting XML-RPC method, slipping past the incomplete CVE-2026-34916 filter to load attacker-influenced code. The server executes the injected code, giving the attacker full control of the host. No public exploit is confirmed, but the low attack complexity and multiple reported variants make a working exploit plausible.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 26, 2026

Remote code execution in Revive Adserver is reachable by authenticated low-privilege users who bypass the prior fix for CVE-2026-34916, either by supplying a disallowed-but-valid plugin identifier in the type parameter or by abusing the ox.setChannelTargeting XML-RPC API method. The flaw lets an attacker inject and execute arbitrary code (CWE-94) on the server, fully compromising confidentiality, integrity, and availability. Reported via HackerOne by multiple researchers (including phucrio and offsetmd); no public exploit identified at time of analysis and the issue is not listed in CISA KEV.

RemediationAI

No vendor-released patch version is identified in the available data, so a specific upgrade target cannot be cited; monitor the official Revive Adserver security advisories and the linked HackerOne reports (https://hackerone.com/reports/3780854, https://hackerone.com/reports/3781492) and apply the corrected fix as soon as it is published, since this CVE demonstrates the earlier CVE-2026-34916 fix is incomplete. As compensating controls until a fix lands, restrict or disable the XML-RPC interface (which exposes the ox.setChannelTargeting method) at the web-server or application layer - this blocks one of the two known vectors but breaks any legitimate XML-RPC integrations; additionally, tighten account provisioning and revoke unnecessary low-privilege accounts to remove the PR:L foothold the attack depends on, and place the admin/API surface behind network ACLs or a VPN so it is not internet-reachable, accepting that remote operators will then need the VPN to manage campaigns.

Affected VersionsENISA

Adserver 0 ≤6.0.7

Affected Packages

euvd adserver no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Revive Adserver is an open-source PHP-based ad-management and ad-serving platform (CPE cpe:2.3:a:revive:adserver). The root cause is CWE-94 (Improper Control of Generation of Code / code injection): the application loads plugin logic based on a caller-supplied plugin type identifier, and the original CVE-2026-34916 patch attempted to restrict which identifiers were permitted. This follow-up vulnerability shows the allow/deny logic is incomplete - a type value that is structurally valid yet not actually allowed still slips through, and the ox.setChannelTargeting XML-RPC method exposes a second, equivalent path into the same code-loading sink. Because plugin identifiers ultimately map to executable code, controlling them yields arbitrary code execution.

Know when Adserver gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hackerone) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable code injection needs only a low-privilege account (PR:L) and no interaction; arbitrary code execution yields full C/I/A impact with low complexity.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (hackerone).

CVSS VectorVendor: hackerone

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

DescriptionCVE.org

Bypass to the fix for CVE-2026-34916. Variants of such vectors have been also reported by phucrio and offsetmd. The fix can be bypassed either by sending a disallowed but otherwise valid plugin identifier as type, or using the ox.setChannelTargeting XML-RPC API method.

Executive ViewAI

Why It Matters

Revive Adserver contains a remote code execution vulnerability (CVE-2026-50741) that allows authenticated low-privilege users to execute arbitrary code on ad server instances, bypassing previous security patches. Organizations relying on Revive Adserver for ad delivery operations face complete compromise of server confidentiality, integrity, and availability. No vendor patch is currently available, creating immediate operational risk and requiring interim protective measures.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: Restrict network access to Revive Adserver administration interfaces to authorized internal IPs only; disable XML-RPC API if not operationally required; implement Web Application Firewall rules to detect and block injection attempts in the 'type' parameter and suspicious API calls; enforce principle of least privilege-audit and minimize low-privilege user accounts with server access; deploy real-time process execution monitoring to detect unexpected code execution; implement network segmentation to limit lateral movement if compromise occurs; monitor authentication logs for brute-force or privilege escalation patterns.

Threat Intelligence Overview

EPSS Score
0.3%
Top 76% exploitable
Prevalence
Low
niche open-source ad-serving platform, limited enterprise footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy