{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24899 exists.","fix":"No fix has been published for CVE-2025-24899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24899 is a high-severity vulnerability in yogeshojha rengine, published on 3 Feb 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-24899 and fix it if it is affected.\n\nWhat it is: CVE-2025-24899 is a high-severity vulnerability in yogeshojha rengine, published on 3 Feb 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-24899 exists.\n\nAffected product: yogeshojha rengine. 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-24899/ (Markdown: https://insights.sbomify.com/CVE-2025-24899/index.md)","id":"CVE-2025-24899","markdown":"https://insights.sbomify.com/CVE-2025-24899/index.md","name":"CVE-2025-24899","record":{"aliases":["GHSA-r3fp-xr9f-wv38"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"reNgine recon framework","requires_auth":"low_privilege","summary":"An insider attacker can extract sensitive user information like credentials and roles via an API endpoint in reNgine.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rengine","vendor":"yogeshojha"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"reNgine is an automated reconnaissance framework for web applications. A vulnerability was discovered in reNgine, where **an insider attacker with any role** (such as Auditor, Penetration Tester, or Sys Admin) **can extract sensitive information from other reNgine users.** After running a scan and obtaining vulnerabilities from a target, the attacker can retrieve details such as `username`, `password`, `email`, `role`, `first name`, `last name`, `status`, and `activity information` by making a GET request to `/api/listVulnerability/`. This issue has been addressed in version 2.2.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","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":"Disclosure of Sensitive User Information via API in reNgine","id":"CVE-2025-24899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Concorde CSRF vulnerability due to insecure configuration of authentication cookie attributes","id":"CVE-2025-24900"},"packages":[],"prev":{"headline":"rust openssl ssl::select_next_proto use after free","id":"CVE-2025-24898"},"products":["rengine"],"published":"2025-02-03","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-36566","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-28995","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2021-38606","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":8.8,"headline":"Business Logic And Unrestricted Project Deletion Lead To Take Over the System in reNgine","id":"CVE-2025-24968","kev_date_added":null,"published":"2025-02-04"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-50094","kev_date_added":null,"published":"2024-01-01"},{"cvss_score":8.7,"headline":"reNgine 2.2.0 Authenticated Command Injection via Scan Engine Configuration","id":"CVE-2024-58287","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":8.7,"headline":"Command Injection in reNgine","id":"CVE-2025-24962","kev_date_added":null,"published":"2025-02-03"}],"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":"2025-02-12","vendors":["yogeshojha"]},"summary":"An insider attacker can extract sensitive user information like credentials and roles via an API endpoint in reNgine.","url":"https://insights.sbomify.com/CVE-2025-24899/"}