{"answers":{"affected":"2 open source packages ship an affected version, including yapi-vendor. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-36686 exists.","fix":"No fix has been published for CVE-2021-36686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-36686 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2023. 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-36686 and fix it if it is affected.\n\nWhat it is: CVE-2021-36686 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jan 2023. Any signed-in user can exploit it over the network, 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-2021-36686 exists.\n\nAffected packages and fixed versions:\n- yapi-vendor (npm): affected all versions up to 1.9.1; no fix listed\n- yapi-vendor (npm): affected all versions up to 1.9.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-36686/ (Markdown: https://insights.sbomify.com/CVE-2021-36686/index.md)","id":"CVE-2021-36686","markdown":"https://insights.sbomify.com/CVE-2021-36686/index.md","name":"CVE-2021-36686","record":{"aliases":["CVE-2021-33237","GHSA-4jqw-vfmj-9rmh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"YAPI API management","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code via XSS in the YAPI interface API edit page, compromising user sessions and data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yapi","vendor":"ymfe"}],"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":"Cross Site Scripting (XSS) vulnerability in yapi 1.9.1 allows attackers to execute arbitrary code via the /interface/api edit page.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site Scripting in yapi-vendor","id":"CVE-2021-36686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2021-36689"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.9.1"],"package":"yapi-vendor","purl":null,"source":"GHSA-4jqw-vfmj-9rmh"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.9.1"],"package":"yapi-vendor","purl":"pkg:npm/yapi-vendor","source":"GHSA-4jqw-vfmj-9rmh"}],"prev":{"headline":"Open redirect in n/a","id":"CVE-2021-36668"},"products":["n/a"],"published":"2023-01-26","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-70059","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":7.4,"headline":"yapi disables TLS/SSL certificate validation via rejectUnauthorized: false in Axios HTTPS agent","id":"CVE-2025-70058","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-70060","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":5.4,"headline":"Cross-site Scripting in yapi-vendor","id":"CVE-2018-17574","kev_date_added":null,"published":"2018-09-28"},{"cvss_score":5.1,"headline":"Weak JSON Web Token in yapi-vendor","id":"CVE-2021-27884","kev_date_added":null,"published":"2021-03-01"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-01","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via XSS in the YAPI interface API edit page, compromising user sessions and data.","url":"https://insights.sbomify.com/CVE-2021-36686/"}