{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-52916 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52916 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52916 is a low-severity vulnerability in Yealink RPS, published on 21 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52916 and fix it if it is affected.\n\nWhat it is: CVE-2025-52916 is a low-severity vulnerability in Yealink RPS, published on 21 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52916 in the wild and no public exploit code.\n\nAffected product: Yealink RPS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52916/ (Markdown: https://insights.sbomify.com/CVE-2025-52916/index.md)","id":"CVE-2025-52916","markdown":"https://insights.sbomify.com/CVE-2025-52916/index.md","name":"CVE-2025-52916","record":{"aliases":["GHSA-w9xp-xgf9-cvcf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Yealink RPS","requires_auth":"high_privilege","summary":"Attackers can brute-force enumerate device serial numbers due to missing attempt limits in Yealink RPS, potentially exposing device information.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Yealink RPS before 2025-06-04 lacks SN verification attempt limits, enabling brute-force enumeration (last five digits).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in RPS","id":"CVE-2025-52916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in RPS","id":"CVE-2025-52917"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-52915"},"products":["RPS"],"published":"2025-06-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-28","vendors":["Yealink"]},"summary":"Attackers can brute-force enumerate device serial numbers due to missing attempt limits in Yealink RPS, potentially exposing device information.","url":"https://insights.sbomify.com/CVE-2025-52916/"}