CVE-2026-50741

Plugin Identifier Injection Bypass in Revive Adserver

Published Jun 26, 2026 CVSS 3.0 · 8.8 High EPSS 4.9% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A bypass of the previously applied CVE‑2026‑34916 fix allows an attacker to supply an otherwise syntactically correct but disallowed plugin identifier as the type field, or to invoke the ox.setChannelTargeting XML‑RPC method, thereby activating a plugin that should be rejected. The flaw corresponds to CWE‑94 – code injection via untrusted input – and enables execution of arbitrary code in the context of the Revive Adserver server. This allows full compromise of the underlying host operating system.

Affected Systems

Any Revive Adserver deployment that has not applied the CVE‑2026‑34916 patch is potentially vulnerable. The vendor list identifies Revive:Adserver as the affected product, but no specific version range is supplied, so administrators must verify whether their installations include the remediation. All installations that expose the plugin validation endpoint or the XML‑RPC API to external actors remain at risk.

Risk and Exploitability

The CVSS score of 8.8 indicates high severity, while the EPSS score of 4% suggests a low but non‑negligible likelihood of exploitation in the current window. The vulnerability is not listed in the CISA KEV catalog, but that does not reduce its threat. Remote exploitation is possible by sending crafted requests to the plugin validation path or the XML‑RPC endpoint, assuming the server is reachable from an attacker. In typical deployments where the server is internet‑exposed or accessible from untrusted networks, the risk escalates; however, network segmentation or firewall policies can mitigate the attack surface.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Revive Adserver version that contains the CVE‑2026‑34916 fix.
  • If an immediate upgrade is not feasible, implement strict validation of plugin identifiers to reject any values not explicitly allowed by the current policy.
  • Restrict external access to the XML‑RPC API through firewall rules or IP whitelisting to limit the attack surface.

Generated by OpenCVE AI on August 3, 2026 at 07:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Plugin Identifier Injection Bypass in Revive Adserver
Type Values Removed Values Added
Title Revive Adserver Bypass of Plugin Validation Allows Code Execution (CWE‑94)
Type Values Removed Values Added
Title Revive Adserver Bypass of Plugin Validation Allows Code Execution (CWE‑94)
Type Values Removed Values Added
Title Revive Adserver Code Injection Bypass via Plugin ID or XML‑RPC
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Revive
Revive adserver
Vendors & Products Revive
Revive adserver
Type Values Removed Values Added
Title Revive Adserver Code Injection Bypass via Plugin ID or XML‑RPC
Type Values Removed Values Added
Description 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.
Weaknesses CWE-94
References
Metrics cvssV3_0

{'score': 8.8, 'vector': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Jun 26, 2026, 12:27 PM
Reserved
Jun 6, 2026, 3:00 PM
Status
Analyzed
Published
Jun 26, 2026, 2:16 AM
Modified
Oct 25, 2026, 10:10 PM