{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10275 exists.","fix":"No fix has been published for CVE-2025-10275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10275 is a medium-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 12 Sep 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-10275 and fix it if it is affected.\n\nWhat it is: CVE-2025-10275 is a medium-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 12 Sep 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-10275 exists.\n\nAffected product: YunaiV yudao-cloud. 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-10275/ (Markdown: https://insights.sbomify.com/CVE-2025-10275/index.md)","id":"CVE-2025-10275","markdown":"https://insights.sbomify.com/CVE-2025-10275/index.md","name":"CVE-2025-10275","record":{"aliases":["GHSA-4vcj-8cj2-68x6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"yudao-cloud CRM","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in the CRM transfer feature to modify business ownership records remotely.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"yudao-cloud","vendor":"iocoder"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A weakness has been identified in YunaiV yudao-cloud up to 2025.09. This affects an unknown part of the file /crm/business/transfer. Executing a manipulation of the argument ids/newOwnerUserId can lead to improper authorization. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. It is recommended to upgrade the affected component. The vendor confirms: \"[T]he current code already checks the functional update permission, uses the authenticated server-side user ID, requires CRM OWNER permission, and explicitly rejects non-owner transfers in the shared transfer service, except for authorized CRM administrators.\"","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":"YunaiV yudao-cloud transfer improper authorization","id":"CVE-2025-10275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10276"},"packages":[],"prev":{"headline":"erjinzhi 10OA item cross site scripting","id":"CVE-2025-10274"},"products":["yudao-cloud"],"published":"2025-09-12","related":[{"cvss_score":5.3,"headline":"YunaiV yudao-cloud HTTP Request transfer improper authorization","id":"CVE-2025-10987","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":5.3,"headline":"YunaiV yudao-cloud submit improper authorization","id":"CVE-2025-10277","kev_date_added":null,"published":"2025-09-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2026-10-27","vendors":["YunaiV"]},"summary":"Attackers can bypass authorization checks in the CRM transfer feature to modify business ownership records remotely.","url":"https://insights.sbomify.com/CVE-2025-10275/"}