{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61319 exists.","fix":"No fix has been published for CVE-2025-61319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61319 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Oct 2025. 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-2025-61319 and fix it if it is affected.\n\nWhat it is: CVE-2025-61319 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Oct 2025. 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-2025-61319 exists.\n\nAffected product: n/a. 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-61319/ (Markdown: https://insights.sbomify.com/CVE-2025-61319/index.md)","id":"CVE-2025-61319","markdown":"https://insights.sbomify.com/CVE-2025-61319/index.md","name":"CVE-2025-61319","record":{"aliases":["GHSA-2hpc-g4g6-34jm"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ReNgine web UI","requires_auth":"none","summary":"Stored XSS in ReNgine allows attackers to execute arbitrary JavaScript in the administrator's browser, potentially stealing session cookies or taking over accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rengine","vendor":"yogeshojha"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ReNgine thru 2.2.0 is vulnerable to a Stored Cross-Site Scripting (XSS) vulnerability in the Vulnerabilities module. When scanning a target with an XSS payload, the unsanitized payload is rendered in the ReNgine web UI, resulting in arbitrary JavaScript execution in the victim's browser. This can be abused to steal session cookies, perform unauthorized actions, or compromise the ReNgine administrator's account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-09","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-09T19:24:51Z","kind":"github_poc","ref":"https://github.com/AmalJafarzade/CVE-2025-61319","stars":0,"title":"Stored XSS in ReNgine \u003c= 2.2.0 — public disclosure"}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-61319","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-61330"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-61318"},"products":["n/a"],"published":"2025-10-10","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-10","vendors":["n/a"]},"summary":"Stored XSS in ReNgine allows attackers to execute arbitrary JavaScript in the administrator's browser, potentially stealing session cookies or taking over accounts.","url":"https://insights.sbomify.com/CVE-2025-61319/"}