{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7907 exists.","fix":"No fix has been published for CVE-2025-7907 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-7907 is a medium-severity vulnerability in Ruoyi Ruoyi, published on 20 Jul 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-7907 and fix it if it is affected.\n\nWhat it is: CVE-2025-7907 is a medium-severity vulnerability in Ruoyi Ruoyi, published on 20 Jul 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-7907 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-7907/ (Markdown: https://insights.sbomify.com/CVE-2025-7907/index.md)","id":"CVE-2025-7907","markdown":"https://insights.sbomify.com/CVE-2025-7907/index.md","name":"CVE-2025-7907","record":{"aliases":["GHSA-r3pp-w9mm-8fcc"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RuoYi admin panel","requires_auth":"low_privilege","summary":"Attackers can access the Druid monitoring console using default credentials in the configuration file, bypassing authentication.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"ruoyi","vendor":"ruoyi"}],"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:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-1392","name":"Use of Default Credentials"}],"description":"A vulnerability was found in yangzongzhuan RuoYi up to 4.8.1. It has been classified as problematic. Affected is an unknown function of the file ruoyi-admin/src/main/resources/application-druid.yml of the component Druid. The manipulation leads to use of default credentials. It is possible to launch the attack remotely. 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":"yangzongzhuan RuoYi Druid application-druid.yml default credentials","id":"CVE-2025-7907","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ruoyi:ruoyi","products":["ruoyi:ruoyi"],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"D-Link DI-8100 jhttpd ddns.asp sprintf stack-based overflow","id":"CVE-2025-7908"},"packages":[],"prev":{"headline":"yangzongzhuan RuoYi CommonController.java uploadFile unrestricted upload","id":"CVE-2025-7906"},"products":["RuoYi"],"published":"2025-07-20","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-07-21","vendors":["yangzongzhuan"]},"summary":"Attackers can access the Druid monitoring console using default credentials in the configuration file, bypassing authentication.","url":"https://insights.sbomify.com/CVE-2025-7907/"}