CVE-2025-55128: Revive Adserver · Vulnerability
Affects Revive AdserverSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Revive Revive Adserver | Affected
| Fixed in– |
AI-suggested
1. Restrict and monitor admin access strictly, employing strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. 2. Implement rate limiting or input validation on the userlog-index.php page to cap the maximum number of items per page, preventing excessive resource consumption. 3. Regularly audit and monitor server performance and logs for unusual spikes in resource usage or large requests targeting the admin interface. 4. If possible, isolate the ad server environment to limit the impact of potential DoS conditions on other critical systems. 5. Stay updated with Revive Adserver vendor announcements for patches or official fixes and apply them promptly once available. 6. Consider implementing web application firewalls (WAF) rules to detect and block abnormal request patterns targeting the admin interface. 7. Educate administrators on the risks of this vulnerability and encourage best practices for credential security and session management.
Description
HackerOne community member Dang Hung Vi (vidang04) has reported an uncontrolled resource consumption vulnerability in the “userlog-index.php”. An attacker with access to the admin interface could request an arbitrarily large number of items per page, potentially leading to a denial of service.