{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52919 exists.","fix":"No fix has been published for CVE-2025-52919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52919 is a medium-severity vulnerability in Yealink RPS, published on 21 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52919 and fix it if it is affected.\n\nWhat it is: CVE-2025-52919 is a medium-severity vulnerability in Yealink RPS, published on 21 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52919 exists.\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-52919/ (Markdown: https://insights.sbomify.com/CVE-2025-52919/index.md)","id":"CVE-2025-52919","markdown":"https://insights.sbomify.com/CVE-2025-52919/index.md","name":"CVE-2025-52919","record":{"aliases":["GHSA-h483-pm62-h98h"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Yealink RPS","requires_auth":"low_privilege","summary":"Attackers can upload invalid certificates due to insufficient validation in Yealink RPS, potentially bypassing security controls.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"In Yealink RPS before 2025-05-26, the certificate upload function does not properly validate certificate content, potentially allowing invalid certificates to be uploaded.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"File upload in RPS","id":"CVE-2025-52919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in InnoShop","id":"CVE-2025-52920"},"packages":[],"prev":{"headline":"Missing authorization in RPS","id":"CVE-2025-52918"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-28","vendors":["Yealink"]},"summary":"Attackers can upload invalid certificates due to insufficient validation in Yealink RPS, potentially bypassing security controls.","url":"https://insights.sbomify.com/CVE-2025-52919/"}