{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43381 exists.","fix":"No fix has been published for CVE-2024-43381 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-43381 is a medium-severity cross-site scripting vulnerability in yogeshojha rengine, published on 16 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-43381 and fix it if it is affected.\n\nWhat it is: CVE-2024-43381 is a medium-severity cross-site scripting vulnerability in yogeshojha rengine, published on 16 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-43381 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-2024-43381/ (Markdown: https://insights.sbomify.com/CVE-2024-43381/index.md)","id":"CVE-2024-43381","markdown":"https://insights.sbomify.com/CVE-2024-43381/index.md","name":"CVE-2024-43381","record":{"aliases":["GHSA-96q4-fj2m-jqf7"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"reNgine recon framework","requires_auth":"none","summary":"Attackers can execute malicious scripts in the reNgine dashboard by poisoning DNS records, potentially compromising user accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rengine","vendor":"yogeshojha"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-87","name":"Improper Neutralization of Alternate XSS Syntax"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"reNgine is an automated reconnaissance framework for web applications. Versions 2.1.2 and prior are susceptible to Stored Cross-Site Scripting (XSS) attacks. This vulnerability occurs when scanning a domain, and if the target domain's DNS record contains an XSS payload, it leads to the execution of malicious scripts in the reNgine's dashboard view when any user views the scan results. The XSS payload is directly fetched from the DNS record of the remote target domain. Consequently, an attacker can execute the attack without requiring any additional input from the target or the reNgine user. A patch is available and expected to be part of version 2.1.3.","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":"reNgine vulnerable to Stored Cross-Site Scripting (XSS) via DNS Record Poisoning","id":"CVE-2024-43381","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Snowflake JDBC Security Advisory","id":"CVE-2024-43382"},"packages":[],"prev":{"headline":"fugit parse and parse_nat stall on lengthy input","id":"CVE-2024-43380"},"products":["rengine"],"published":"2024-08-16","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":"2024-08-16","vendors":["yogeshojha"]},"summary":"Attackers can execute malicious scripts in the reNgine dashboard by poisoning DNS records, potentially compromising user accounts.","url":"https://insights.sbomify.com/CVE-2024-43381/"}