{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-52263 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52263 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52263 is a high-severity vulnerability in n/a, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52263 and fix it if it is affected.\n\nWhat it is: CVE-2025-52263 is a high-severity vulnerability in n/a, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52263 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-2025-52263/ (Markdown: https://insights.sbomify.com/CVE-2025-52263/index.md)","id":"CVE-2025-52263","markdown":"https://insights.sbomify.com/CVE-2025-52263/index.md","name":"CVE-2025-52263","record":{"aliases":["GHSA-qpr3-rq65-76fj"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charging station","requires_auth":"low_privilege","summary":"Authenticated attackers can upload malicious firmware to the EV charger, resulting in arbitrary code execution on the device.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"An issue in the Web Configuration module of Startcharge Artemis AC Charger 7-22 kW v1.0.4 allows authenticated network-adjacent attackers to upload crafted firmware, leading to arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2025-52263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-52264"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2025-52239"},"products":["n/a"],"published":"2025-10-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-27","vendors":["n/a"]},"summary":"Authenticated attackers can upload malicious firmware to the EV charger, resulting in arbitrary code execution on the device.","url":"https://insights.sbomify.com/CVE-2025-52263/"}