{"answers":{"affected":"2 open source packages ship an affected version, including verbb/comments. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-13869 in the wild and no public exploit code.","fix":"Upgrade verbb/comments to 1.5.5 or later.","what":"CVE-2020-13869 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jun 2020. 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-2020-13869 and fix it if it is affected.\n\nWhat it is: CVE-2020-13869 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jun 2020. 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-2020-13869 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- verbb/comments (Packagist): affected all versions; fixed in 1.5.5\n- verbb/comments (Packagist): affected all versions; fixed in 1.5.5\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-2020-13869/ (Markdown: https://insights.sbomify.com/CVE-2020-13869/index.md)","id":"CVE-2020-13869","markdown":"https://insights.sbomify.com/CVE-2020-13869/index.md","name":"CVE-2020-13869","record":{"aliases":["GHSA-jhhf-c849-3rh2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Craft CMS plugin","requires_auth":"low_privilege","summary":"Stored XSS in Craft CMS Comments plugin allows attackers to inject scripts via guest names, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"comments","vendor":"verbb"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","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":"An issue was discovered in the Comments plugin before 1.5.6 for Craft CMS. There is stored XSS via a guest name.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Comments plugin stored Cross-site Scripting via a guest name","id":"CVE-2020-13869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Comments plugin stored Cross-site Scripting (XSS) via an asset volume name","id":"CVE-2020-13870"},"packages":[{"ecosystem":"Packagist","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"verbb/comments","purl":null,"source":"GHSA-jhhf-c849-3rh2"},{"ecosystem":"Packagist","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"verbb/comments","purl":"pkg:composer/verbb/comments","source":"GHSA-jhhf-c849-3rh2"}],"prev":{"headline":"Comments plugin Cross-Site Request Forgery (CSRF)","id":"CVE-2020-13868"},"products":["n/a"],"published":"2020-06-05","related":[{"cvss_score":6.5,"headline":"Comments plugin Cross-Site Request Forgery (CSRF)","id":"CVE-2020-13868","kev_date_added":null,"published":"2020-06-05"},{"cvss_score":5.4,"headline":"Comments plugin stored Cross-site Scripting (XSS) via an asset volume name","id":"CVE-2020-13870","kev_date_added":null,"published":"2020-06-05"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Stored XSS in Craft CMS Comments plugin allows attackers to inject scripts via guest names, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2020-13869/"}