{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-5751 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5751 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5751 is a medium-severity vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 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-5751 and fix it if it is affected.\n\nWhat it is: CVE-2025-5751 is a medium-severity vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 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-5751 in the wild and no public exploit code.\n\nAffected product: WOLFBOX Level 2 EV Charger. 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-5751/ (Markdown: https://insights.sbomify.com/CVE-2025-5751/index.md)","id":"CVE-2025-5751","markdown":"https://insights.sbomify.com/CVE-2025-5751/index.md","name":"CVE-2025-5751","record":{"aliases":["GHSA-jcc3-259c-x5c2"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"EV charger management card","requires_auth":"none","summary":"Physically present attackers can bypass authentication on WOLFBOX Level 2 EV Chargers due to non-personalized management cards with hard-coded credentials.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"level_2_ev_charger_firmware","vendor":"wolfbox"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability. This vulnerability allows physically present attackers to bypass authentication on affected installations of WOLFBOX Level 2 EV Charger. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the handling of management cards. The issue results from the lack of personalization of management cards. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26292.","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":"WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability","id":"CVE-2025-5751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Vertical scroll image slideshow gallery","id":"CVE-2025-5752"},"packages":[],"prev":{"headline":"Memory corruption in Level 2 EV Charger","id":"CVE-2025-5750"},"products":["Level 2 EV Charger"],"published":"2025-06-06","related":[{"cvss_score":8.8,"headline":"Memory corruption in Level 2 EV Charger","id":"CVE-2025-5750","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":8,"headline":"WOLFBOX Level 2 EV Charger MCU Command Parsing Misinterpretation of Input Remote Code Execution Vulnerability","id":"CVE-2025-5747","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":8,"headline":"WOLFBOX Level 2 EV Charger LAN OTA Exposed Dangerous Method Remote Code Execution Vulnerability","id":"CVE-2025-5748","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":6.3,"headline":"WOLFBOX Level 2 EV Charger BLE Encryption Keys Uninitialized Variable Authentication Bypass Vulnerability","id":"CVE-2025-5749","kev_date_added":null,"published":"2025-06-06"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-06","vendors":["WOLFBOX"]},"summary":"Physically present attackers can bypass authentication on WOLFBOX Level 2 EV Chargers due to non-personalized management cards with hard-coded credentials.","url":"https://insights.sbomify.com/CVE-2025-5751/"}