dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-52918

MEDIUM · 5.0 CVSS v3.1 Published 2025-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Yealink RPS before 2025-05-26 does not prevent OpenAPI access by frozen enterprise accounts, allowing unauthorized access to deactivated interfaces.

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 · moderate confidence

Yealink RPS has an authorization flaw where frozen enterprise accounts can still access OpenAPI endpoints, allowing unauthorized interaction with interfaces that should be deactivated. This is an access control bypass vulnerability affecting systems before the 2025-05-26 patch.

MitigationImplement proper authorization checks to deny OpenAPI access for frozen enterprise accounts and ensure all deactivated interfaces are inaccessible regardless of account status.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Yealink RPS installation
    Locate the Yealink RPS server in your environment and confirm it is the Remote Provisioning Server product
    Affected if The system is running Yealink RPS software
  2. Check RPS version or patch date
    Access the RPS admin interface or check system files to determine the installed version or last patch date
    Affected if Version is unknown or patch was applied before 2025-05-26
  3. Identify enterprise accounts
    Review the RPS user management section to list all enterprise accounts configured in the system
    Affected if One or more enterprise accounts exist in the RPS
  4. Check for frozen account status
    Inspect each enterprise account to determine if any have been set to frozen or disabled status
    Affected if At least one enterprise account is in frozen/disabled state
  5. Test OpenAPI access with frozen account
    Attempt to authenticate to RPS OpenAPI endpoints using credentials from a frozen enterprise account
    Affected if The frozen account successfully authenticates and can access OpenAPI endpoints

If the system is Yealink RPS with a version/patch prior to 2025-05-26 and has frozen enterprise accounts that can still access OpenAPI endpoints, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks to deny OpenAPI access for frozen enterprise accounts and ensure all deactivated interfaces are inaccessible regardless of account status.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52918 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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