{"answers":{"affected":"2 open source packages ship an affected version, including github.com/leanote/leanote. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-4263 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-4263 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-4263 is a low-severity cross-site scripting vulnerability in leanote, published on 21 Dec 2022. 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-2021-4263 and fix it if it is affected.\n\nWhat it is: CVE-2021-4263 is a low-severity cross-site scripting vulnerability in leanote, published on 21 Dec 2022. 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-2021-4263 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/leanote/leanote (Go): affected all versions up to 2.6.1; no fix listed\n- github.com/leanote/leanote (Go): affected all versions up to 2.6.1; no fix listed\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-2021-4263/ (Markdown: https://insights.sbomify.com/CVE-2021-4263/index.md)","id":"CVE-2021-4263","markdown":"https://insights.sbomify.com/CVE-2021-4263/index.md","name":"CVE-2021-4263","record":{"aliases":["GHSA-6cmv-2548-82v4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Leanote note-taking app","requires_auth":"low_privilege","summary":"Remote attackers can inject malicious scripts via the history.js define function in Leanote, potentially executing code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"leanote","vendor":"leanote"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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, which was classified as problematic, has been found in leanote 2.6.1. This issue affects the function define of the file public/js/plugins/history.js. The manipulation of the argument content leads to cross site scripting. The attack may be initiated remotely. The identifier of the patch is 0f9733c890077942150696dcc6d2b1482b7a0a19. It is recommended to apply a patch to fix this issue. The identifier VDB-216461 was assigned to this vulnerability.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"leanote history.js define cross site scripting","id":"CVE-2021-4263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"xss","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"LinkedIn dustjs prototype pollution","id":"CVE-2021-4264"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["2.6.1"],"package":"github.com/leanote/leanote","purl":null,"source":"GHSA-6cmv-2548-82v4"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["2.6.1"],"package":"github.com/leanote/leanote","purl":"pkg:golang/github.com/leanote/leanote","source":"GHSA-6cmv-2548-82v4"}],"prev":{"headline":"laravel-jqgrid EloquentRepositoryAbstract.php getRows sql injection","id":"CVE-2021-4262"},"products":["leanote"],"published":"2022-12-21","related":[{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2020-26157","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2020-26158","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-43721","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":6.1,"headline":"Cross-site scripting in Leanote","id":"CVE-2019-1010003","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-18553","kev_date_added":null,"published":"2018-10-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-1000459","kev_date_added":null,"published":"2018-01-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-04-14","vendors":["n/a"]},"summary":"Remote attackers can inject malicious scripts via the history.js define function in Leanote, potentially executing code in victim browsers.","url":"https://insights.sbomify.com/CVE-2021-4263/"}