CVE-2026-34914
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 · uneditedA missing sanitisation of user input in the zone-include.php script of Revive Adserver 6.0.6 and earlier. A low‑privileged user could exploit the clientid parameter to perform blind SQL injection attacks. Input sanitisation has been improved to ensure that all parameters processed by the script are 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 confidenceRevive Adserver 6.0.6 and earlier contains a blind SQL injection vulnerability in zone-include.php. The clientid parameter is not properly sanitized, allowing low-privileged authenticated users to inject malicious SQL queries.
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
- Low
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Revive Adserver installationCheck for the presence of the Revive Adserver web application files, typically in the web root directory. Look for the main entry points like index.php or admin/index.php.Affected if The application is installed and accessible on the server.
-
Determine installed versionCheck the version file or header. Common locations include a VERSION file in the root directory, or inspect the main index.php or admin/index.php for a version constant. Alternatively, check the database configuration for version information.Affected if The installed version is 6.0.6 or any earlier version.
-
Locate vulnerable scriptVerify the existence of zone-include.php in the web accessible directories, typically under /www/pages/ or similar path based on installation.Affected if The file zone-include.php exists in the web application directory.
-
Verify low-privileged user accessCheck if the application allows creation or existence of low-privileged user accounts that can access the zone management functionality. Review user role definitions in the administration panel or database.Affected if Low-privileged authenticated users have access to the zone-include.php functionality.
-
Inspect clientid parameter handlingExamine the zone-include.php source code to confirm the clientid parameter is used in SQL queries without proper sanitization. Search for direct use of $_GET or $_REQUEST['clientid'] in SQL statements.Affected if The clientid parameter is used in SQL queries without parameterized statements or input validation.
A user is affected if they run Revive Adserver version 6.0.6 or earlier, the zone-include.php file exists, and low-privileged users can access it.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of Revive Adserver that includes proper input validation for the clientid parameter. If immediate upgrade is not possible, disable low-privileged user access until the patch can be applied.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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