{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52045 exists.","fix":"No fix has been published for CVE-2023-52045 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-52045 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 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-2023-52045 and fix it if it is affected.\n\nWhat it is: CVE-2023-52045 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 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-2023-52045 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-2023-52045/ (Markdown: https://insights.sbomify.com/CVE-2023-52045/index.md)","id":"CVE-2023-52045","markdown":"https://insights.sbomify.com/CVE-2023-52045/index.md","name":"CVE-2023-52045","record":{"aliases":["GHSA-mq5w-h63c-48mj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"File manager","requires_auth":"none","summary":"Attackers can inject persistent scripts via filename bypass in eLfinder, potentially leading to session hijacking or malicious code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"elfinder","vendor":"std42"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Studio-42 eLfinder 2.1.62 contains a filename restriction bypass leading to a persistent Cross-site Scripting (XSS) vulnerability.","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":"Cross-site scripting in n/a","id":"CVE-2023-52045","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-52046"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2023-52044"},"products":["n/a"],"published":"2024-10-31","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-52044","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":9.8,"headline":"Studio 42 elFinder vulnerable to Incorrect Access Control","id":"CVE-2024-38909","kev_date_added":null,"published":"2024-07-30"},{"cvss_score":9.8,"headline":"RCE in Studio-42 elFinder on Windows before 2.1.61","id":"CVE-2022-27115","kev_date_added":null,"published":"2022-04-11"},{"cvss_score":9.8,"headline":"elFinder Unrestricted File Upload vulnerability","id":"CVE-2021-43421","kev_date_added":null,"published":"2022-04-07"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities leading to RCE","id":"CVE-2021-32682","kev_date_added":null,"published":"2021-06-14"},{"cvss_score":9.8,"headline":"elFinder command injection vulnerability in the PHP connector","id":"CVE-2019-9194","kev_date_added":null,"published":"2019-02-26"},{"cvss_score":9.1,"headline":"Path Traversal in Studio-42 elFinder through 2.1.60","id":"CVE-2022-26960","kev_date_added":null,"published":"2022-03-21"}],"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-11-01","vendors":["n/a"]},"summary":"Attackers can inject persistent scripts via filename bypass in eLfinder, potentially leading to session hijacking or malicious code execution.","url":"https://insights.sbomify.com/CVE-2023-52045/"}