{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41392 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41392 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41392 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Oct 2022. 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-2022-41392 and fix it if it is affected.\n\nWhat it is: CVE-2022-41392 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-41392 in the wild and no public exploit code.\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-2022-41392/ (Markdown: https://insights.sbomify.com/CVE-2022-41392/index.md)","id":"CVE-2022-41392","markdown":"https://insights.sbomify.com/CVE-2022-41392/index.md","name":"CVE-2022-41392","record":{"aliases":["GHSA-6c4g-j5rf-mc73"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"TotalJS web framework","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts via XSS in the Website name field of TotalJS, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"total.js","vendor":"totaljs"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","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 cross-site scripting (XSS) vulnerability in TotalJS commit 8c2c8909 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Website name text field under Main Settings.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2022-41392","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2022-41395"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2022-41391"},"products":["n/a"],"published":"2022-10-07","related":[{"cvss_score":9.8,"headline":"Arbitrary Code Execution","id":"CVE-2021-23389","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":9.8,"headline":"Remote Code Execution (RCE)","id":"CVE-2021-23344","kev_date_added":null,"published":"2021-03-04"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2024-48655","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-44019","kev_date_added":null,"published":"2022-10-29"},{"cvss_score":8.6,"headline":"Command Injection","id":"CVE-2020-28494","kev_date_added":null,"published":"2021-02-02"},{"cvss_score":7.5,"headline":"Code injection in total.js","id":"CVE-2021-32831","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":7.5,"headline":"Path Traversal in total.js","id":"CVE-2019-8903","kev_date_added":null,"published":"2019-02-18"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts via XSS in the Website name field of TotalJS, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2022-41392/"}