{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70368 exists.","fix":"No fix has been published for CVE-2025-70368 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70368 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-70368 and fix it if it is affected.\n\nWhat it is: CVE-2025-70368 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2026. Any signed-in user can exploit it over the network, 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-70368 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-70368/ (Markdown: https://insights.sbomify.com/CVE-2025-70368/index.md)","id":"CVE-2025-70368","markdown":"https://insights.sbomify.com/CVE-2025-70368/index.md","name":"CVE-2025-70368","record":{"aliases":["GHSA-rxx2-x5v3-hv94"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Worklenz project management","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts into Project Updates, leading to code execution in victims' browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"worklenz","vendor":"worklenz"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"Worklenz version 2.1.5 contains a Stored Cross-Site Scripting (XSS) vulnerability in the Project Updates feature. An attacker can submit a malicious payload in the Updates text field which is then rendered in the reporting view without proper sanitization. Malicious JavaScript may be executed in a victim's browser when they browse to the page containing the vulnerable field.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-01-24","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-24T00:48:32Z","kind":"github_poc","ref":"https://github.com/Stolichnayer/CVE-2025-70368","stars":0,"title":"Worklenz version 2.1.5 Stored Cross-Site Scripting (XSS)"}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-70368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-70397"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-70365"},"products":["n/a"],"published":"2026-01-26","related":[{"cvss_score":8.8,"headline":"Worklenz Boolean-Based Blind SQL Injection via Improper ORDER BY Clause Input Validation","id":"CVE-2026-25947","kev_date_added":null,"published":"2026-02-10"}],"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":"2026-01-27","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts into Project Updates, leading to code execution in victims' browsers.","url":"https://insights.sbomify.com/CVE-2025-70368/"}