CVE-2025-28172
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGrandstream 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Grandstream Networks UCM6510 IP PBX firmware versions 1.0.20.52 and before lacks proper rate limiting or account lockout mechanisms on its authentication interface. An attacker with network access to the device's web interface or SIP endpoints can submit unlimited login attempts with different passwords until successfully guessing valid credentials, enabling account compromise via brute force.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.20.52CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the UCM6510 firmware versionLog into the device web interface and navigate to System Settings > System Info, or access via SSH and run 'get firmversion' or similar command to retrieve the installed firmware versionAffected if The displayed firmware version is 1.0.20.52 or any version number lower (for example 1.0.20.51, 1.0.19.x, etc.)
-
Verify web interface network exposureCheck the device network configuration through the web interface under Network Settings > Basic Settings to determine if the HTTP/HTTPS management interface is bound to a WAN or externally accessible IP addressAffected if The web interface is reachable from untrusted networks (not restricted to LAN-only access)
-
Confirm rate limiting absence on authenticationNavigate to Account Settings or Security Settings in the web interface and look for any rate limiting configuration options related to login attempts or authentication throttlingAffected if No rate limiting or login attempt throttling options are present or configurable in the administrative interface
-
Confirm account lockout mechanism absenceNavigate to Account Settings or Security Settings and look for account lockout, failed login timeout, or password attempt lockout configuration optionsAffected if No account lockout policy or failed login attempt lockout feature is available or enabled in the device settings
You are affected if your UCM6510 firmware version is 1.0.20.52 or earlier AND the web interface is network-accessible AND no rate limiting or account lockout mechanisms are configured on the device.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement account lockout policies after a configurable number of failed login attempts and add rate limiting to authentication endpoints; if available, update to a patched firmware version that addresses this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data