{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50876 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-50876 and fix it if it is affected.\n\nWhat it is: CVE-2026-50876 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-50876 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-2026-50876/ (Markdown: https://insights.sbomify.com/CVE-2026-50876/index.md)","id":"CVE-2026-50876","markdown":"https://insights.sbomify.com/CVE-2026-50876/index.md","name":"CVE-2026-50876","record":{"aliases":["GHSA-rqwf-4646-gmv2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Deck9 Input","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary web scripts or HTML in Deck9 Input via a crafted payload, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"A cross-site scripting (XSS) vulnerability in Deck9 Input v2.0.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload.","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":"Cross-site scripting in n/a","id":"CVE-2026-50876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2026-50877"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-50875"},"products":["n/a"],"published":"2026-06-15","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":"partial"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["n/a"]},"summary":"Attackers can execute arbitrary web scripts or HTML in Deck9 Input via a crafted payload, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2026-50876/"}