CVE-2026-34916: Revive Adserver PHP Code Injection via Delivery Limitations
Revive Adserver versions 6.0.6 and earlier contain a code injection vulnerability in the delivery limitation feature. A low-privileged user can craft a malicious request that inserts PHP code into the database, which is then executed when serving ads. The vulnerability stems from inadequate validation of the logical parameter used to configure delivery restrictions. This is a serious issue because it allows an authenticated attacker to achieve remote code execution on the ad server with full system privileges.
Source data · NVD / CISA · public domain
- CVSS
- 3.0 · 8.8 HIGH · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-94
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-23 / 2026-06-23
NVD description (verbatim)
A missing validation of user input when saving delivery limitations in Revive Adserver 6.0.6 and earlier could allow a low‑privileged user to use the logical parameter to inject malicious PHP code into the compiledlimitations field on the database and have it executed during banner delivery. Input sanitisation has been improved to ensure that the parameter is properly validated.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-34916 is a PHP code injection vulnerability (CWE-94: Improper Control of Generation of Code) affecting Revive Adserver 6.0.6 and earlier. When saving delivery limitations, the logical parameter is not properly validated before being stored in the compiledlimitations database field. During banner delivery, the stored content is executed as PHP code, allowing an attacker with low-privilege access to inject arbitrary code. The vulnerability requires authentication and does not require user interaction, resulting in a CVSS 3.0 score of 8.8 (HIGH severity) with network-accessible impact affecting confidentiality, integrity, and availability.
Business impact
This vulnerability enables authenticated attackers to establish persistent code execution on ad-serving infrastructure. An attacker could steal advertiser data, modify banner content to redirect traffic or serve malware, disrupt ad campaigns, or use the compromised server as a pivot point into the broader network. For organizations running Revive Adserver—particularly ad networks, agencies, and publishers—this represents a direct threat to revenue operations, brand reputation, and customer trust. The ability to modify banner delivery means attackers could silently alter advertising behavior, leading to undetected fraud or data exfiltration.
Affected systems
Revive Adserver versions 6.0.6 and earlier are affected. Vendor product information is not yet cataloged in the source data; consult the official Revive Adserver security advisory to confirm the complete version matrix. Any deployment where low-privileged users have access to the delivery limitations configuration interface is at risk. This includes self-hosted instances and managed deployments that have not applied the patched version.
Exploitability
The vulnerability requires valid authentication credentials and low privilege level access, making it exploitable by a disgruntled employee, compromised account, or lateral-movement attacker who has already gained initial access to the ad server environment. No user interaction is required and the attack is network-accessible, meaning exploitation can occur remotely. The logical parameter manipulation is straightforward to execute once privilege is obtained, making this a practical and reliable attack vector. The vulnerability is not currently tracked in the CISA Known Exploited Vulnerabilities catalog, but the simplicity of exploitation and the high value of ad server compromise suggest it is likely to be weaponized.
Remediation
Upgrade Revive Adserver to a patched version that includes improved input sanitization for the logical parameter. Verify the specific patched version number against the official Revive Adserver security advisory. Until patching is possible, implement strict access controls to limit who can modify delivery limitation settings, restrict network access to the ad server management interface, and monitor database and log activity for suspicious parameter patterns. Consider temporarily disabling the delivery limitation feature if it is not critical to operations.
Patch guidance
Apply the vendor's patched version of Revive Adserver as soon as possible. The fix includes proper validation of the logical parameter before database storage. Organizations should test the patch in a staging environment to ensure compatibility with existing ad campaigns and customizations before deploying to production. Verify the patch version against the official Revive Adserver security bulletin to ensure authenticity. Monitor the application logs after patching to confirm that the validation is functioning correctly.
Detection guidance
Search for suspicious patterns in logs and database queries targeting the compiledlimitations field. Look for user activity modifying delivery limitation settings from unusual locations or at unusual times. Monitor for error logs or warnings related to PHP execution or parameter validation failures. Database audit logs may reveal INSERT or UPDATE statements containing PHP code fragments or suspicious serialized objects in the logical parameter. Additionally, monitor banner serving infrastructure for unexpected PHP execution errors or performance anomalies that could indicate injected code execution.
Why prioritize this
This vulnerability merits immediate patching due to its high CVSS score (8.8), the low authentication requirement, and the severe impact on confidentiality, integrity, and availability. Revive Adserver is critical infrastructure for advertising operations, and code execution on such systems directly threatens customer data, advertising integrity, and business continuity. The attack is practical and does not require sophisticated exploitation techniques. Organizations running affected versions should treat this as a critical security priority.
Risk score, explained
The CVSS 3.0 score of 8.8 (HIGH) reflects network-accessible attack surface, low privilege requirement, no user interaction needed, and maximum impact across all three security objectives. The vulnerability allows full code execution in the context of the application, enabling attackers to read, modify, or delete any data accessible to the Revive Adserver process. While authentication is required, the low privilege level means the risk extends beyond administrators to a broader class of users, substantially increasing exposure.
Frequently asked questions
Can this vulnerability be exploited without an account on the Revive Adserver?
No. The vulnerability requires valid authentication credentials with low privilege level. An attacker must have a user account or must first compromise an existing user account to exploit this issue. This reduces but does not eliminate risk, as employee accounts, partner integrations, or weak credentials could provide a foothold.
What does 'low privilege' mean in this context?
Low privilege refers to user accounts that are not administrators. Typically, this includes campaign managers, publishers, or advertiser users who have legitimate access to configure delivery settings but should not have system-level capabilities. The vulnerability allows such users to escalate their access to execute arbitrary server code.
If we restrict access to delivery limitations settings, are we protected?
Restricting access significantly reduces risk by limiting the number of users who can trigger the vulnerability. However, this is a compensating control and not a substitute for patching. A compromised account with the necessary privileges would still be able to exploit the flaw. Patching the input validation is the proper remediation.
How quickly should we patch this?
This should be treated as a critical priority and patched within days, not weeks. The HIGH CVSS score, ease of exploitation, and potential for persistent code execution make this a high-value target for attackers. Test the patch immediately in a non-production environment and schedule production deployment as soon as safely possible.
This analysis is based on the published CVE record and publicly available information as of June 2026. The vendor product list in the source data was not populated; verify affected versions and patch availability against the official Revive Adserver security advisory before taking action. This explainer is for informational purposes and does not constitute security advice specific to your environment. Consult your security team and the vendor directly for guidance on your particular deployment. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-10904HIGHChrome V8 Sandbox Escape Remote Code Execution
- CVE-2026-10928HIGHScript Injection in Google Chrome Headless – CVSS 8.8 High Severity
- CVE-2026-11231HIGHChrome Safe Browsing Code Execution on macOS – Patch Now
- CVE-2026-11688HIGHChrome SVG Sandbox Escape RCE Vulnerability – Patch Urgently
- CVE-2026-1829HIGHContent Visibility for Divi Builder Plugin RCE (v4.02 and below)
- CVE-2026-24155HIGHNVIDIA NeMo Framework Code Injection Vulnerability (CVSS 7.8)
- CVE-2026-25856HIGHOpenBullet2 Authenticated Remote Code Execution Vulnerability
- CVE-2026-41249HIGHCoreShop GitHub Actions RCE via Malicious Pull Request