{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46604 exists.","fix":"No fix has been published for CVE-2022-46604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46604 is a high-severity vulnerability in n/a, published on 2 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-46604 and fix it if it is affected.\n\nWhat it is: CVE-2022-46604 is a high-severity vulnerability in n/a, published on 2 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46604 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-2022-46604/ (Markdown: https://insights.sbomify.com/CVE-2022-46604/index.md)","id":"CVE-2022-46604","markdown":"https://insights.sbomify.com/CVE-2022-46604/index.md","name":"CVE-2022-46604","record":{"aliases":["GHSA-q3q6-m34m-pq3r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Responsive FileManager","requires_auth":"low_privilege","summary":"Attackers can bypass file extension checks to upload malicious PHP files, resulting in arbitrary code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"responsive_filemanager","vendor":"tecrail"}],"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":"An issue in Tecrail Responsive FileManager v9.9.5 and below allows attackers to bypass the file extension check mechanism and upload a crafted PHP file, leading to arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-02-03","github_poc":2,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-02-03T08:56:16Z","kind":"github_poc","ref":"https://github.com/galoget/ResponsiveFileManager-CVE-2022-46604","stars":6,"title":"Responsive FileManager v.9.9.5 vulnerable to CVE-2022-46604."},{"date":"2025-06-05T02:30:04Z","kind":"github_poc","ref":"https://github.com/CyberQuestor-infosec/CVE-2022-46604-Responsive-File-Manager","stars":1,"title":null},{"date":"2023-04-05","kind":"exploitdb","ref":"51251","stars":null,"title":"Responsive FileManager 9.9.5 - Remote Code Execution (RCE)"}],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2022-46604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Supply chain in n/a","id":"CVE-2022-46609"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2022-46603"},"products":["n/a"],"published":"2023-02-02","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-44276","kev_date_added":null,"published":"2023-06-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-10567","kev_date_added":null,"published":"2020-03-14"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2020-10212","kev_date_added":null,"published":"2020-03-06"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2018-14728","kev_date_added":null,"published":"2018-08-03"},{"cvss_score":8.6,"headline":"Server-side request forgery in n/a","id":"CVE-2018-18867","kev_date_added":null,"published":"2018-10-31"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2018-20789","kev_date_added":null,"published":"2019-02-25"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["n/a"]},"summary":"Attackers can bypass file extension checks to upload malicious PHP files, resulting in arbitrary code execution on the server.","url":"https://insights.sbomify.com/CVE-2022-46604/"}