{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51401 exists.","fix":"No fix has been published for CVE-2025-51401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51401 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 2025. 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-51401 and fix it if it is affected.\n\nWhat it is: CVE-2025-51401 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Jul 2025. 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-51401 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-51401/ (Markdown: https://insights.sbomify.com/CVE-2025-51401/index.md)","id":"CVE-2025-51401","markdown":"https://insights.sbomify.com/CVE-2025-51401/index.md","name":"CVE-2025-51401","record":{"aliases":["GHSA-f57q-2vg6-g2qp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Live Helper Chat","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts via stored XSS in the chat transfer operator name field, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"live_helper_chat","vendor":"livehelperchat"}],"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":"A stored cross-site scripting (XSS) vulnerability in the chat transfer function of Live Helper Chat v4.60 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the operator name parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2025-07-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-20T08:51:58Z","kind":"github_poc","ref":"https://github.com/Thewhiteevil/CVE-2025-51401","stars":0,"title":"LiveHelperChat \u003c=4.61 - Stored Cross Site Scripting (XSS) via Operator Chat Name Field Triggers on Chat Owner Transfer"},{"date":"2025-07-22","kind":"exploitdb","ref":"52380","stars":null,"title":"LiveHelperChat 4.61 - Stored Cross Site Scripting (XSS) via the Chat Transfer Function"}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-51401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-51403"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-51400"},"products":["n/a"],"published":"2025-07-21","related":[{"cvss_score":9.8,"headline":"livehelperchat Server-Side Template Injection","id":"CVE-2024-27516","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":8.8,"headline":"Host Header injection in password Reset in livehelperchat/livehelperchat","id":"CVE-2022-0935","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":8.8,"headline":"XSS in livehelperchat in livehelperchat/livehelperchat","id":"CVE-2022-1234","kev_date_added":null,"published":"2022-04-06"},{"cvss_score":8.7,"headline":"SSRF on index.php/cobrowse/proxycss/ in livehelperchat/livehelperchat","id":"CVE-2022-1191","kev_date_added":null,"published":"2022-03-31"},{"cvss_score":7.7,"headline":"SSRF filter bypass port 80, 433 in livehelperchat/livehelperchat","id":"CVE-2022-1213","kev_date_added":null,"published":"2022-04-05"},{"cvss_score":7.5,"headline":"Weak secrethash can be brute-forced in livehelperchat/livehelperchat","id":"CVE-2022-1235","kev_date_added":null,"published":"2022-04-05"},{"cvss_score":7.5,"headline":"Loose comparison causes IDOR on multiple endpoints in livehelperchat/livehelperchat","id":"CVE-2022-1176","kev_date_added":null,"published":"2022-03-31"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-22","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts via stored XSS in the chat transfer operator name field, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2025-51401/"}