{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24731 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24731 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24731 is a critical missing authorization vulnerability in ev2go.io, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24731 and fix it if it is affected.\n\nWhat it is: CVE-2026-24731 is a critical missing authorization vulnerability in ev2go.io, published on 26 Feb 2026. 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-2026-24731 in the wild and no public exploit code.\n\nAffected product: ev2go.io. 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-2026-24731/ (Markdown: https://insights.sbomify.com/CVE-2026-24731/index.md)","id":"CVE-2026-24731","markdown":"https://insights.sbomify.com/CVE-2026-24731/index.md","name":"CVE-2026-24731","record":{"aliases":["GHSA-627v-rfr6-xm8w"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"EV charging platform","requires_auth":"none","summary":"Unauthenticated attackers can impersonate charging stations via WebSocket endpoints to manipulate backend data and control infrastructure.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"ev2go.io","vendor":"ev2go"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"WebSocket endpoints lack proper authentication mechanisms, enabling \nattackers to perform unauthorized station impersonation and manipulate \ndata sent to the backend. An unauthenticated attacker can connect to the\n OCPP WebSocket endpoint using a known or discovered charging station \nidentifier, then issue or receive OCPP commands as a legitimate charger.\n Given that no authentication is required, this can lead to privilege \nescalation, unauthorized control of charging infrastructure, and \ncorruption of charging network data reported to the backend.","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":"EV2GO ev2go.io Missing Authentication for Critical Function","id":"CVE-2026-24731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Improper permission checks in Extension:NSFileRepo","id":"CVE-2026-24732"},"packages":[],"prev":{"headline":"Interinfo DreamMaker - Unrestricted Upload of File with Dangerous Type","id":"CVE-2026-24729"},"products":["ev2go.io"],"published":"2026-02-26","related":[{"cvss_score":8.7,"headline":"EV2GO ev2go.io Improper Restriction of Excessive Authentication Attempts","id":"CVE-2026-25945","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":6.9,"headline":"EV2GO ev2go.io Insufficient Session Expiration","id":"CVE-2026-20895","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":6.9,"headline":"EV2GO ev2go.io Insufficiently Protected Credentials","id":"CVE-2026-22890","kev_date_added":null,"published":"2026-02-26"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-05","vendors":["EV2GO"]},"summary":"Unauthenticated attackers can impersonate charging stations via WebSocket endpoints to manipulate backend data and control infrastructure.","url":"https://insights.sbomify.com/CVE-2026-24731/"}