{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10567 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10567 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10567 is a critical vulnerability in n/a, published on 14 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10567 and fix it if it is affected.\n\nWhat it is: CVE-2020-10567 is a critical vulnerability in n/a, published on 14 Mar 2020. 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-2020-10567 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-2020-10567/ (Markdown: https://insights.sbomify.com/CVE-2020-10567/index.md)","id":"CVE-2020-10567","markdown":"https://insights.sbomify.com/CVE-2020-10567/index.md","name":"CVE-2020-10567","record":{"aliases":["GHSA-r65x-vmq7-cgg6"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Responsive Filemanager","requires_auth":"none","summary":"Attackers can execute arbitrary PHP code by uploading a JPEG with malicious EXIF data and renaming it to .php via the save_img action.","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":9.8,"severity":"critical","source":"nvd","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-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Responsive Filemanager through 9.14.0. In the ajax_calls.php file in the save_img action in the name parameter, there is no validation of what kind of extension is sent. This makes it possible to execute PHP code if a legitimate JPEG image contains this code in the EXIF data, and the .php extension is used in the name parameter. (A potential fast patch is to disable the save_img action in the config file.)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-26","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-26T11:18:08Z","kind":"github_poc","ref":"https://github.com/PierreAdams/CVE-2020-10567","stars":4,"title":"RCE RESPONSIVE filemanager v.9.14.0"}],"tier":"poc_unverified"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2020-10567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-10568"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-10566"},"products":["n/a"],"published":"2020-03-14","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":"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.8,"headline":"File upload in n/a","id":"CVE-2022-46604","kev_date_added":null,"published":"2023-02-02"},{"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary PHP code by uploading a JPEG with malicious EXIF data and renaming it to .php via the save_img action.","url":"https://insights.sbomify.com/CVE-2020-10567/"}