{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5701 exists.","fix":"No fix has been published for CVE-2023-5701 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5701 is a medium-severity cross-site scripting vulnerability in vnotex vnote, published on 23 Oct 2023. 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-2023-5701 and fix it if it is affected.\n\nWhat it is: CVE-2023-5701 is a medium-severity cross-site scripting vulnerability in vnotex vnote, published on 23 Oct 2023. 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-2023-5701 exists.\n\nAffected product: vnotex vnote. 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-2023-5701/ (Markdown: https://insights.sbomify.com/CVE-2023-5701/index.md)","id":"CVE-2023-5701","markdown":"https://insights.sbomify.com/CVE-2023-5701/index.md","name":"CVE-2023-5701","record":{"aliases":["GHSA-cxg7-94vc-m5j2"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Markdown editor","requires_auth":"none","summary":"An attacker can execute arbitrary JavaScript in the vnote Markdown editor by tricking a user into opening a malicious file.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"vnote","vendor":"vnote_project"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A vulnerability has been found in vnotex vnote up to 3.17.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Markdown File Handler. The manipulation with the input \u003cxss onclick=\"alert(1)\" style=display:block\u003eClick here\u003c/xss\u003e leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-243139. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.","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":"vnotex vnote Markdown File cross site scripting","id":"CVE-2023-5701","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Viessmann Vitogate 300 direct request","id":"CVE-2023-5702"},"packages":[],"prev":{"headline":"Netentsec NS-ASG Application Security Gateway uploadiscgwrouteconf.php sql injection","id":"CVE-2023-5700"},"products":["vnote"],"published":"2023-10-23","related":[{"cvss_score":8.6,"headline":"VNote vulnerable to Markdown XSS, which leads to RCE","id":"CVE-2024-41662","kev_date_added":null,"published":"2024-07-24"},{"cvss_score":6.1,"headline":"VNote 2.2 has XSS via a new text note.","id":"CVE-2019-8419","kev_date_added":null,"published":"2019-02-17"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-09-12","vendors":["vnotex"]},"summary":"An attacker can execute arbitrary JavaScript in the vnote Markdown editor by tricking a user into opening a malicious file.","url":"https://insights.sbomify.com/CVE-2023-5701/"}