# CVE-2025-52669: Information disclosure in Revive Adserver

> Non-admin users can view other users' contact names and email addresses due to insecure design policies in Revive Adserver.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-8xf9-935r-5f85

## What is CVE-2025-52669?

CVE-2025-52669 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 20 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insecure design policies in the user management system of Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes non-admin users to have access to the contact name and email address of other users on the system.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-52669?

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

## How do I fix CVE-2025-52669?

No fix has been published for CVE-2025-52669 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52669 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52669 exists.

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52669 and fix it if it is affected.

What it is: CVE-2025-52669 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 20 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52669 exists.

Affected product: Revive-Adserver Revive Adserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52669/ (Markdown: https://insights.sbomify.com/CVE-2025-52669/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52669
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52669
- OSV: https://osv.dev/vulnerability/CVE-2025-52669

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52669/
Summaries are generated and may contain mistakes; the official description above is the record.
