{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-56396 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56396 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56396 is a high-severity vulnerability in Ruoyi Ruoyi, published on 26 Nov 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-56396 and fix it if it is affected.\n\nWhat it is: CVE-2025-56396 is a high-severity vulnerability in Ruoyi Ruoyi, published on 26 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-56396 in the wild and no public exploit code.\n\nAffected product: Ruoyi Ruoyi. 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-56396/ (Markdown: https://insights.sbomify.com/CVE-2025-56396/index.md)","id":"CVE-2025-56396","markdown":"https://insights.sbomify.com/CVE-2025-56396/index.md","name":"CVE-2025-56396","record":{"aliases":["GHSA-xhr6-7rpm-rmv3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"RuoYi admin framework","requires_auth":"low_privilege","summary":"Attackers can gain escalated privileges in RuoYi by exploiting a flaw where the owning department has higher rights than the active user.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ruoyi","vendor":"ruoyi"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered in Ruoyi 4.8.1 allowing attackers to gain escalated privileges due to the owning department having higher rights than the active user.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privilege escalation in n/a","id":"CVE-2025-56396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ruoyi:ruoyi","products":["ruoyi:ruoyi"],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2025-56399"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-56394"},"products":["n/a"],"published":"2025-11-26","related":[{"cvss_score":10,"headline":"SQL injection in n/a","id":"CVE-2024-57521","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28402","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28405","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28406","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-28408","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-28410","kev_date_added":null,"published":"2025-04-07"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-28411","kev_date_added":null,"published":"2025-04-07"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-04","vendors":["n/a"]},"summary":"Attackers can gain escalated privileges in RuoYi by exploiting a flaw where the owning department has higher rights than the active user.","url":"https://insights.sbomify.com/CVE-2025-56396/"}