{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10276 exists.","fix":"No fix has been published for CVE-2025-10276 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10276 is a medium-severity missing authorization vulnerability in YunaiV ruoyi-vue-pro, 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-10276 and fix it if it is affected.\n\nWhat it is: CVE-2025-10276 is a medium-severity missing authorization vulnerability in YunaiV ruoyi-vue-pro, 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-10276 exists.\n\nAffected product: YunaiV ruoyi-vue-pro. 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-10276/ (Markdown: https://insights.sbomify.com/CVE-2025-10276/index.md)","id":"CVE-2025-10276","markdown":"https://insights.sbomify.com/CVE-2025-10276/index.md","name":"CVE-2025-10276","record":{"aliases":["GHSA-2w47-9873-w85f"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web application","requires_auth":"low_privilege","summary":"Attackers can improperly transfer CRM contracts by manipulating user IDs, leading to unauthorized data modification and privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ruoyi-vue-pro","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 security vulnerability has been detected in YunaiV ruoyi-vue-pro up to 2025.09. This vulnerability affects unknown code of the file /crm/contract/transfer. The manipulation of the argument id/newOwnerUserId leads to improper authorization. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. Upgrading the affected component is advised. 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 ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10276","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 yudao-cloud submit improper authorization","id":"CVE-2025-10277"},"packages":[],"prev":{"headline":"YunaiV yudao-cloud transfer improper authorization","id":"CVE-2025-10275"},"products":["ruoyi-vue-pro"],"published":"2025-09-12","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2022-37158","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.3,"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10988","kev_date_added":null,"published":"2025-09-26"},{"cvss_score":5.3,"headline":"YunaiV ruoyi-vue-pro transfer improper authorization","id":"CVE-2025-10278","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-permanent path traversal","id":"CVE-2025-2742","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-temporary path traversal","id":"CVE-2025-2743","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":5.3,"headline":"zhijiantianya ruoyi-vue-pro Material Upload Interface upload-news-image path traversal","id":"CVE-2025-2744","kev_date_added":null,"published":"2025-03-25"}],"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":"total"},"state":"PUBLISHED","updated":"2026-10-27","vendors":["YunaiV"]},"summary":"Attackers can improperly transfer CRM contracts by manipulating user IDs, leading to unauthorized data modification and privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-10276/"}