{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24967 exists.","fix":"No fix has been published for CVE-2025-24967 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24967 is a high-severity cross-site scripting vulnerability in yogeshojha rengine, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24967 and fix it if it is affected.\n\nWhat it is: CVE-2025-24967 is a high-severity cross-site scripting vulnerability in yogeshojha rengine, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24967 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-24967/ (Markdown: https://insights.sbomify.com/CVE-2025-24967/index.md)","id":"CVE-2025-24967","markdown":"https://insights.sbomify.com/CVE-2025-24967/index.md","name":"CVE-2025-24967","record":{"aliases":["GHSA-23wx-5q5w-334w"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"reNgine recon framework","requires_auth":"high_privilege","summary":"Attackers can inject malicious scripts via usernames, leading to script execution when admins view user entries in the reNgine admin panel.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rengine","vendor":"yogeshojha"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"reNgine is an automated reconnaissance framework for web applications. A stored cross-site scripting (XSS) vulnerability exists in the admin panel's user management functionality. An attacker can exploit this issue by injecting malicious payloads into the username field during user creation. This vulnerability allows unauthorized script execution whenever the admin views or interacts with the affected user entry, posing a significant risk to sensitive admin functionalities. This issue affects all versions up to and including 2.20. Users are advised to monitor the project for future releases which address this issue. There are no known workarounds.","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":"Stored XSS on Admin Panel When Deleting a User in reNgine","id":"CVE-2025-24967","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Business Logic And Unrestricted Project Deletion Lead To Take Over the System in reNgine","id":"CVE-2025-24968"},"packages":[],"prev":{"headline":"HTML Injection in reNgine","id":"CVE-2025-24966"},"products":["rengine"],"published":"2025-02-04","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":"partial"},"state":"PUBLISHED","updated":"2025-02-04","vendors":["yogeshojha"]},"summary":"Attackers can inject malicious scripts via usernames, leading to script execution when admins view user entries in the reNgine admin panel.","url":"https://insights.sbomify.com/CVE-2025-24967/"}