{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-19007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-19007 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 2020. 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-2020-19007 and fix it if it is affected.\n\nWhat it is: CVE-2020-19007 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Aug 2020. 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-2020-19007 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-2020-19007/ (Markdown: https://insights.sbomify.com/CVE-2020-19007/index.md)","id":"CVE-2020-19007","markdown":"https://insights.sbomify.com/CVE-2020-19007/index.md","name":"CVE-2020-19007","record":{"aliases":["GHSA-j97g-76wm-6mpj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Halo blog","requires_auth":"low_privilege","summary":"Attackers can inject malicious JavaScript into blog comments, executing code in victims' browsers via the Halo blog platform.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"halo","vendor":"halo"}],"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":"Halo blog 1.2.0 allows users to submit comments on blog posts via /api/content/posts/comments. The javascript code supplied by the attacker will then execute in the victim user's browser.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2020-19007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2020-19028"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-19005"},"products":["n/a"],"published":"2020-08-26","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-32994","kev_date_added":null,"published":"2022-06-27"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-32995","kev_date_added":null,"published":"2022-06-27"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-18980","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-21522","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-21523","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-21526","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2025-44594","kev_date_added":null,"published":"2025-09-09"}],"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-04","vendors":["n/a"]},"summary":"Attackers can inject malicious JavaScript into blog comments, executing code in victims' browsers via the Halo blog platform.","url":"https://insights.sbomify.com/CVE-2020-19007/"}