{"answers":{"affected":"2 open source packages ship an affected version, including simogeo/filemanager. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46001 exists.","fix":"No fix has been published for CVE-2025-46001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46001 is a critical vulnerability in n/a, published on 18 Jul 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-2025-46001 and fix it if it is affected.\n\nWhat it is: CVE-2025-46001 is a critical vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46001 exists.\n\nAffected packages and fixed versions:\n- simogeo/filemanager (Packagist): affected all versions; no fix listed\n- simogeo/filemanager (Packagist): affected all versions; no fix listed\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-2025-46001/ (Markdown: https://insights.sbomify.com/CVE-2025-46001/index.md)","id":"CVE-2025-46001","markdown":"https://insights.sbomify.com/CVE-2025-46001/index.md","name":"CVE-2025-46001","record":{"aliases":["GHSA-m5hw-rhvr-f47c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Filemanager PHP library","requires_auth":"none","summary":"Attackers can execute arbitrary code by uploading a crafted PHP file due to insufficient file type validation in the Filemanager library.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"filemanager","vendor":"simogeo"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"An arbitrary file upload vulnerability in the is_allowed_file_type() function of Filemanager v2.3.0 allows attackers to execute arbitrary code via uploading a crafted PHP file.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"simogeo/filemanager arbitrary file upload vulnerability","id":"CVE-2025-46001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Filemanager is vulnerable to Relative Path Traversal through filemanager.php","id":"CVE-2025-46002"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":[],"package":"simogeo/filemanager","purl":null,"source":"GHSA-m5hw-rhvr-f47c"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":[],"package":"simogeo/filemanager","purl":"pkg:composer/simogeo/filemanager","source":"GHSA-m5hw-rhvr-f47c"}],"prev":{"headline":"File upload in n/a","id":"CVE-2025-46000"},"products":["n/a"],"published":"2025-07-18","related":[{"cvss_score":6.5,"headline":"File upload in n/a","id":"CVE-2025-46000","kev_date_added":null,"published":"2025-07-18"},{"cvss_score":6.5,"headline":"Filemanager is vulnerable to Relative Path Traversal through filemanager.php","id":"CVE-2025-46002","kev_date_added":null,"published":"2025-07-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-23","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading a crafted PHP file due to insufficient file type validation in the Filemanager library.","url":"https://insights.sbomify.com/CVE-2025-46001/"}