{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-50620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-50620 is a high-severity vulnerability in n/a, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-50620 and fix it if it is affected.\n\nWhat it is: CVE-2024-50620 is a high-severity vulnerability in n/a, published on 11 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-50620 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-2024-50620/ (Markdown: https://insights.sbomify.com/CVE-2024-50620/index.md)","id":"CVE-2024-50620","markdown":"https://insights.sbomify.com/CVE-2024-50620/index.md","name":"CVE-2024-50620","record":{"aliases":["GHSA-h9c8-jr46-gp7p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"CIPPlanner CIPAce","requires_auth":"low_privilege","summary":"Authorized users can upload executable files via rich text or document management, potentially leading to code execution if storage permissions are misconfigured.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cipace","vendor":"cipplanner"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted Upload of File with Dangerous Type vulnerabilities exist in the rich text editor and document manage components in CIPPlanner CIPAce before 9.17. An authorized user can upload executable files when inserting images in the rich text editor, and upload executable files when uploading files on the document management page. Those executables can be executed if they are not stored in a shared directory or if the storage directory has executed permissions.","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":"File upload in n/a","id":"CVE-2024-50620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cleo Multiple Products Unrestricted File Upload","id":"CVE-2024-50623"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2024-50619"},"products":["n/a"],"published":"2026-02-11","related":[{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2020-11586","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-11597","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-11598","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-50619","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2024-50617","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-11587","kev_date_added":null,"published":"2020-04-06"}],"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-12","vendors":["n/a"]},"summary":"Authorized users can upload executable files via rich text or document management, potentially leading to code execution if storage permissions are misconfigured.","url":"https://insights.sbomify.com/CVE-2024-50620/"}