CVE-2025-55126: Revive Adserver · Cross-site Scripting
Affects Revive AdserverSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Revive Revive Adserver | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-55126, European organizations should implement the following specific measures: 1) Immediately audit all instances of Revive Adserver version 6 to identify exposure to the vulnerability. 2) Apply any official patches or updates released by the Revive project as soon as they become available. 3) In the absence of patches, implement strict input validation and output encoding on campaign name fields to prevent injection of malicious scripts. 4) Deploy Content Security Policies (CSP) that restrict the execution of inline scripts and limit sources of executable code to trusted domains. 5) Conduct regular security reviews and penetration testing focused on web application vulnerabilities, including XSS. 6) Educate administrators and users about the risks of XSS and encourage cautious handling of campaign names and other user-generated content. 7) Monitor web server and application logs for suspicious activity indicative of exploitation attempts. 8) Consider isolating the adserver environment or restricting access to trusted IP ranges to reduce exposure. 9) Integrate web application firewalls (WAF) with rules designed to detect and block XSS payloads targeting the adserver. 10) Maintain an incident response plan to quickly address any detected exploitation attempts.
Description
HackerOne community member Dang Hung Vi (vidang04) has reported a stored XSS vulnerability involving the navigation box at the top of advertiser-related pages, with campaign names being the vector for the stored XSS