dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-34916

HIGH · 8.8 CVSS v3.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Revive Adserver versions 6.0.6 and earlier lack input validation on the logical parameter when saving delivery limitations, allowing low-privileged users to inject malicious PHP code into the compiledlimitations database field. This injected code is then executed during banner delivery, leading to remote code execution.

MitigationApply the vendor patch that improves input sanitization for the delivery limitations logical parameter. If immediate patching is not possible, restrict low-privileged user permissions to the delivery limitations feature until the fix is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Revive Adserver installation and version
    Locate the Revive Adserver installation directory and check the version.php or changelog file. Common paths include /var/www/html/adserver or similar web root directories. Look for a version file or check the admin interface login page footer for the version number.
    Affected if The installed version is 6.0.6 or any version earlier than 6.0.6 (e.g., 6.0.5, 6.0.0, 5.x series).
  2. Verify delivery limitations feature accessibility
    Check if the delivery limitations feature is accessible to low-privileged users by examining user role permissions in the admin panel under 'Users' > 'Admin UI' or by inspecting the database table that stores user permissions.
    Affected if Low-privileged users (non-admin) have write access to the delivery limitations configuration.
  3. Inspect database for suspicious compiledlimitations entries
    Query the database table storing delivery limitations (typically 'acls' or similar limitations table) and examine the 'compiledlimitations' field for any PHP code patterns such as '<?php', 'eval(', 'base64_decode', shell execution functions, or unusual serialized data that may indicate injection.
    Affected if The compiledlimitations field contains unexpected PHP code, serialized payloads, or code that was not intentionally configured by administrators.
  4. Review audit logs for delivery limitation changes
    Check Revive Adserver logs (typically in var/ logs/ directory) for any recent modifications to delivery limitations made by low-privileged users, focusing on the logical parameter during limit creation or editing.
    Affected if There are log entries showing delivery limitation modifications by users who should not have this capability or that show unusual logical parameter values.

You are affected if Revive Adserver version 6.0.6 or earlier is installed AND low-privileged users have access to modify delivery limitations, or if suspicious PHP code is found in the compiledlimitations database field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch that improves input sanitization for the delivery limitations logical parameter. If immediate patching is not possible, restrict low-privileged user permissions to the delivery limitations feature until the fix is deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34916 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34916 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data