Revive Adserver
CVE-2025-52664
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account
-
ExploitSubmit crafted SQLi payload to endpoint
-
ExecutionInjected SQL alters backend query
-
ImpactExfiltrate or modify database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated session as a logged-in user of Revive Adserver 6.0.0 (CVSS PR:L), per both the vector and the description - it is NOT exploitable by unauthenticated anonymous visitors. No special non-default configuration is indicated by the available data; the vulnerable code path appears reachable by standard authenticated users. The primary limiting factor is therefore credential possession: deployments that restrict account creation and protect existing low-privilege accounts substantially reduce exposure, while instances allowing self-registration or hosting many untrusted advertiser/agency accounts are at materially higher risk. No user interaction by a victim is required (UI:N). |
| Impact | This is a genuine priority for any organization running Revive Adserver 6.0.0, though not a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity attack requiring only low privileges - consistent with the description's 'logged in users' qualifier, meaning any authenticated account (including low-trust ad agency/advertiser accounts) suffices. The high impact triad (C:H/I:H/A:H) is credible for SQL injection (CWE-89), which can read, modify, or destroy database contents. Publicly available exploit code (HackerOne report #3395221) meaningfully raises real-world risk by lowering the skill barrier. However, no EPSS score was provided and the CVE is NOT listed in CISA KEV, so there is no evidence of active exploitation - POC availability and active exploitation are distinct signals and should not be conflated. The limiting factor is the PR:L authentication requirement: an attacker needs valid credentials, so exposure is largely confined to instances with untrusted or weakly-protected user accounts, or to post-credential-compromise scenarios. Net: a real, patch-now issue for exposed multi-user deployments, but the authentication gate makes it less wormable than an unauthenticated flaw of the same score. |
| Exploit ScenarioDerived | An attacker with any valid low-privilege Revive Adserver account (e.g., an advertiser or agency login) submits a specifically crafted input containing SQL metacharacters to a vulnerable endpoint, which is concatenated unsafely into a backend database query. Because public exploit code exists (HackerOne #3395221), the attacker can readily extract sensitive data such as credentials or campaign data, tamper with records, or disrupt the service. The low attack complexity and network vector mean exploitation is reliable once credentials are held. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Authenticated SQL injection in Revive Adserver 6.0.0 allows a logged-in user to execute crafted payloads that can disrupt the ad server or access information beyond their authorization. Exploitation requires a valid low-privilege session (CVSS PR:L) and no victim interaction; publicly available exploit code exists, and deployments allowing self-registration or hosting many untrusted advertiser/agency accounts are at materially higher risk. This is a genuine priority for affected organizations, though not a drop-everything emergency, and patch availability reduces urgency once remediation is scheduled.
RemediationAI
Patch available per vendor advisory; apply the vendor patch referenced at http://seclists.org/fulldisclosure/2025/Oct/21, and confirm the exact fixed Revive Adserver release in that advisory because the provided data does not specify a version number. Until upgrading, restrict account creation and tightly control existing low-privilege advertiser/agency accounts, since exploitation requires an authenticated session (PR:L) and does not require victim interaction; this reduces but does not eliminate risk from malicious or compromised legitimate users. Additional compensating controls include monitoring for anomalous SQL-like input in authenticated requests and limiting database privileges for the Revive Adserver account, but these are temporary mitigations and not substitutes for patching. Prioritize internet-facing or multi-tenant instances that permit self-registration, and audit for 6.0.0 exposure.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-89 SQL injection in Revive Adserver 6.0.0, an open-source ad serving platform; the affected CPE is cpe:2.3:a:revive-adserver:revive_adserver:6.0.0:-:*:*:*:*:*:*. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates network-reachable exploitation with low attack complexity, but it requires an authenticated session (PR:L) and no user interaction, with high confidentiality and integrity impact and no scope change. The root cause is insufficient sanitization or parameterization of user-supplied input before it is used in SQL queries, reachable through standard authenticated functionality; no special non-default configuration is indicated by available data. Public exploit code exists via the HackerOne report (https://hackerone.com/reports/3395221), and the vendor patch is referenced at http://seclists.org/fulldisclosure/2025/Oct/21.
Know when Revive Adserver gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable web app, low complexity, requires an authenticated low-privilege account (PR:L per 'logged in users'); SQLi over the shared DB yields full confidentiality, integrity, and availability impact.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
SQL injection in Revive Adserver 6.0.0 causes potential disruption or information access when specifically crafted payloads are sent by logged in users
Executive ViewAI
Organizations running Revive Adserver 6.0.0 face a high-severity, authenticated SQL injection risk that can let low-privilege users disrupt ad delivery or access data beyond their role. With publicly available exploit code, environments that allow self-registration or host many untrusted advertiser/agency accounts should treat this as a priority. A vendor patch is available, so leadership should direct remediation before exposure grows.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Affected Products (CPE)NVD
More in Revive Adserver
View allAn attacker could send a specifically crafted payload to the XML-RPC invocation script and trigger the unserialize() cal
Authorization bypass in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes an logged in attacker to change othe
Use of cryptographically weak PRNG in the password recovery token generation of Revive Adserver < v4.2.1 causes a potent
Multiple cross-site request forgery (CSRF) vulnerabilities in OpenX 2.8.11 and earlier allow remote attackers to hijack
Vulnerability in the generation of session IDs in revive-adserver < 5.3.0, based on the cryptographically insecure uniqi
A security restriction bypass vulnerability has been discovered in Revive Adserver version < 5.0.5 by HackerOne user hoa
HackerOne community member Dang Hung Vi (vidang04) has reported an uncontrolled resource consumption vulnerability in th
Missing authorization check in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes users on the system to delete
Revive Adserver before 4.0.1 allows remote attackers to execute arbitrary code via serialized data in the cookies relate
Reflected cross-site scripting in the Revive Adserver administrative interface (verified against version 5.5.2, with a 6
Improper neutralisation of input in Revive Adserver 6.0.0+ causes a reflected XSS attack in the banner-zone.php script.
Improper Neutralization of Input in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes a potential reflected XS
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB