{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-56156 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-56156 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-56156 is a medium-severity vulnerability in halo-dev halo, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-56156 and fix it if it is affected.\n\nWhat it is: CVE-2024-56156 is a medium-severity vulnerability in halo-dev halo, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-56156 in the wild and no public exploit code.\n\nAffected product: halo-dev halo. 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-2024-56156/ (Markdown: https://insights.sbomify.com/CVE-2024-56156/index.md)","id":"CVE-2024-56156","markdown":"https://insights.sbomify.com/CVE-2024-56156/index.md","name":"CVE-2024-56156","record":{"aliases":["GHSA-99mc-ch53-pqh9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Halo website builder","requires_auth":"none","summary":"Attackers can bypass file validation to upload malicious files, leading to stored XSS and potential remote code execution in Halo.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"halo","vendor":"halo"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L/E:P","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Halo is an open source website building tool. Prior to version 2.20.13, a vulnerability in Halo allows attackers to bypass file type validation controls. This bypass enables the upload of malicious files including executables and HTML files, which can lead to stored cross-site scripting attacks and potential remote code execution under certain circumstances. This issue has been patched in version 2.20.13.","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":"Halo Vulnerable to Stored XSS and RCE via File Upload Bypass","id":"CVE-2024-56156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"iTop vulnerable to Self XSS in CSV Import","id":"CVE-2024-56157"},"packages":[],"prev":{"headline":"Craft CMS Code Injection","id":"CVE-2024-56145"},"products":["halo"],"published":"2025-04-25","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-03","vendors":["halo-dev"]},"summary":"Attackers can bypass file validation to upload malicious files, leading to stored XSS and potential remote code execution in Halo.","url":"https://insights.sbomify.com/CVE-2024-56156/"}