{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45323 exists.","fix":"No fix has been published for CVE-2026-45323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45323 is a critical cross-site scripting vulnerability in jpettitt meshcore-card, published on 28 May 2026. 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-2026-45323 and fix it if it is affected.\n\nWhat it is: CVE-2026-45323 is a critical cross-site scripting vulnerability in jpettitt meshcore-card, published on 28 May 2026. 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-2026-45323 exists.\n\nAffected product: jpettitt meshcore-card. 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-45323/ (Markdown: https://insights.sbomify.com/CVE-2026-45323/index.md)","id":"CVE-2026-45323","markdown":"https://insights.sbomify.com/CVE-2026-45323/index.md","name":"CVE-2026-45323","record":{"aliases":["GHSA-5vrg-xpcj-xppc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Home Assistant plugin","requires_auth":"none","summary":"An attacker within radio range can execute arbitrary JavaScript in the Home Assistant frontend via unescaped node names in the MeshCore Card plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"meshcore_card","vendor":"jpettitt"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"MeshCore Card provides MeshCore Lovelace card for Home Assistant. Prior to 0.3.3, Meshcore node names are rendered without HTML escaping in meshcore-card, allowing any node within direct or indirect (repeated) radio range to execute arbitrary javascript in the Home Assistant frontend of anyone viewing the card. This vulnerability is fixed in 0.3.3.","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":"MeshCore Card: XSS vulnerability through meshcore node name","id":"CVE-2026-45323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Rizin: Double free in cmd_search.c","id":"CVE-2026-45324"},"packages":[],"prev":{"headline":"OS Command Injection in Microsoft UFO Shell Action Replay via Stored Session JSON","id":"CVE-2026-45322"},"products":["meshcore-card"],"published":"2026-05-28","related":[],"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":"total"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["jpettitt"]},"summary":"An attacker within radio range can execute arbitrary JavaScript in the Home Assistant frontend via unescaped node names in the MeshCore Card plugin.","url":"https://insights.sbomify.com/CVE-2026-45323/"}