CVE-2026-34914 is a blind SQL injection vulnerability in Revive Adserver 6.0.6 and earlier. The flaw is caused by missing sanitization of user input in the zone-include.php script. Specifically, a low-privileged user can abuse the clientid parameter to inject SQL in a way that supports blind inference-based attacks against the backend database. The issue is remotely exploitable in the context of an authenticated low-privileged account and stems from insufficient validation and sanitization of parameters processed by zone-include.php.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A blind SQL injection vulnerability in Revive Adserver 6.0.6 and earlier caused by improper input sanitization in zone-include.php, allowing a low-privileged user to exploit the clientid parameter.
A blind SQL injection vulnerability in Revive Adserver allowing a low-privileged user to exploit the clientid parameter in zone-include.php due to insufficient input sanitisation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.