# CVE-2025-28172: Auth bypass in n/a

> Attackers can bypass authentication limits to brute force passwords and gain unauthorized access to Grandstream UCM6510 accounts.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-m4wf-gf4j-873f

## What is CVE-2025-28172?

CVE-2025-28172 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grandstream Networks UCM6510 v1.0.20.52 and before is vulnerable to Improper Restriction of Excessive Authentication Attempts. An attacker can perform an arbitrary number of authentication attempts using different passwords and eventually gain access to the targeted account using a brute force attack.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Grandstream Ucm6510 Firmware.

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

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

## Is CVE-2025-28172 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28171](https://insights.sbomify.com/CVE-2025-28171/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28172 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28172 exists.

Affected product: n/a. 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-28172/ (Markdown: https://insights.sbomify.com/CVE-2025-28172/index.md)
```

## Sources

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

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