{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4819 exists.","fix":"No fix has been published for CVE-2025-4819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4819 is a low-severity missing authorization vulnerability in Ruoyi Ruoyi, published on 17 May 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-4819 and fix it if it is affected.\n\nWhat it is: CVE-2025-4819 is a low-severity missing authorization vulnerability in Ruoyi Ruoyi, published on 17 May 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-4819 exists.\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-4819/ (Markdown: https://insights.sbomify.com/CVE-2025-4819/index.md)","id":"CVE-2025-4819","markdown":"https://insights.sbomify.com/CVE-2025-4819/index.md","name":"CVE-2025-4819","record":{"aliases":["GHSA-wm93-qjx4-vmf3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RuoYi admin framework","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in the offline logout function to force logout other users, requiring high complexity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ruoyi","vendor":"ruoyi"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A vulnerability classified as problematic has been found in y_project RuoYi 4.8.0. Affected is an unknown function of the file /monitor/online/batchForceLogout of the component Offline Logout. The manipulation of the argument ids leads to improper authorization. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"y_project RuoYi Offline Logout batchForceLogout improper authorization","id":"CVE-2025-4819","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ruoyi:ruoyi","products":["ruoyi:ruoyi"],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Incorrect congestion window growth by optimistic ACK","id":"CVE-2025-4820"},"packages":[],"prev":{"headline":"SourceCodester Doctor's Appointment System GET Parameter delete-doctor.php sql injection","id":"CVE-2025-4818"},"products":["RuoYi"],"published":"2025-05-17","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-19","vendors":["y_project"]},"summary":"Attackers can bypass authorization checks in the offline logout function to force logout other users, requiring high complexity.","url":"https://insights.sbomify.com/CVE-2025-4819/"}