CVE-2025-52666VulnerabilityPublished 20 Nov 2025

CVE-2025-52666: Revive Adserver · Vulnerability

Affects Revive AdserverSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Packagistrevive/revive-adserver`pkg:composer/revive/revive-adserver`Other threats	Affected =5.5.2 =6.0.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize upgrading Revive Adserver to versions beyond 6.0.1 or 5.5.2 once patches addressing CVE-2025-52666 are released by the vendor. Until patches are available, administrators should avoid entering or modifying settings with format characters that could trigger the vulnerability. Implement strict input validation and sanitization on the admin interface to prevent malicious format strings. Limit administrator access strictly to trusted personnel and monitor admin activities for unusual configuration changes. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting format string vulnerabilities. Regularly back up configuration data to enable quick restoration if the admin console becomes disabled. Additionally, conduct internal audits to ensure no unauthorized admin accounts exist that could exploit this vulnerability. Finally, maintain up-to-date incident response plans to address potential denial-of-service scenarios affecting administrative access.

Description

Improper neutralisation of format characters in the settings of Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes an administrator user to disable the admin user console due to a fatal PHP error.

Impact

For European organizations, the primary impact of CVE-2025-52666 is administrative disruption. Organizations relying on Revive Adserver for digital advertising may face temporary loss of control over their ad management if the vulnerability is triggered, potentially affecting ad campaign operations and revenue. Since the vulnerability requires administrator privileges, it is unlikely to be exploited by external attackers without prior compromise. However, insider threats or attackers who have gained admin access could leverage this vulnerability to cause denial of service to the admin console. This could delay incident response or ad management activities. The lack of impact on confidentiality or integrity reduces the risk of data breaches or manipulation of ad content. Nonetheless, operational continuity in digital advertising is critical for many European businesses, especially in sectors like media, e-commerce, and marketing agencies. The disruption could also affect compliance with advertising regulations if ad delivery is interrupted.

CWE-134Use of Externally-Controlled Format String (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a function that accepts a format string as an argument, but the format string originates from an external source.
Requirements
Choose a language that is not subject to this flaw.
Implementation
Ensure that all format string functions are passed a static string which cannot be controlled by the user, and that the proper number of arguments are always sent to that function as well. If at all possible, use functions that do not support the %n operator in format strings.
Build and Compilation
Run compilers and linkers with high warning levels, since they may detect incorrect usage.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Format String Injection (opens in a new tab)
String Format Overflow in syslog() (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

hackerone.com/reports/3399218 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Nov 2025, 20:19 UTC

WeaknessesCWE-134

Technical details

References

Community reviews

Related threats