CVE-2025-52670

CVE-2025-52670 is a medium-severity vulnerability in Revive-adserver Revive Adserver with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Description

Missing authorization check in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes users on the system to delete banners owned by other accounts

Frequently asked questions

What is CVE-2025-52670?
Missing authorization check in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes users on the system to delete banners owned by other accounts
How severe is CVE-2025-52670?
CVE-2025-52670 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2025-52670 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-52670?
CVE-2025-52670 affects Revive-adserver Revive Adserver. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-52670?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-52670 have an EU (EUVD) identifier?
Yes. CVE-2025-52670 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198332.
When was CVE-2025-52670 published?
CVE-2025-52670 was published on 2025-11-20 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Revive-adserver Revive Adserver

All CVEs affecting Revive-adserver Revive Adserver →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →