{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25410 exists.","fix":"No fix has been published for CVE-2024-25410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25410 is a medium-severity vulnerability in n/a, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-25410 and fix it if it is affected.\n\nWhat it is: CVE-2024-25410 is a medium-severity vulnerability in n/a, published on 26 Feb 2024. An attacker can exploit it over the internet without logging in, 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-2024-25410 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-2024-25410/ (Markdown: https://insights.sbomify.com/CVE-2024-25410/index.md)","id":"CVE-2024-25410","markdown":"https://insights.sbomify.com/CVE-2024-25410/index.md","name":"CVE-2024-25410","record":{"aliases":["GHSA-hj8r-465g-5vm4"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"flusity-CMS","requires_auth":"none","summary":"Attackers can upload malicious files to flusity-CMS via update_setting.php, potentially leading to remote code execution.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flusity","vendor":"flusity"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"flusity-CMS 2.33 is vulnerable to Unrestricted Upload of File with Dangerous Type in update_setting.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2024-25410","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":"Cross-site scripting in n/a","id":"CVE-2024-25411"},"packages":[],"prev":{"headline":"Business logic in n/a","id":"CVE-2024-25407"},"products":["n/a"],"published":"2024-02-26","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-31666","kev_date_added":null,"published":"2024-04-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-32418","kev_date_added":null,"published":"2024-04-22"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-25502","kev_date_added":null,"published":"2024-02-15"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-23094","kev_date_added":null,"published":"2024-02-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-26350","kev_date_added":null,"published":"2024-02-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-26352","kev_date_added":null,"published":"2024-02-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-25417","kev_date_added":null,"published":"2024-02-11"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-28","vendors":["n/a"]},"summary":"Attackers can upload malicious files to flusity-CMS via update_setting.php, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2024-25410/"}