{"answers":{"affected":"2 open source packages ship an affected version, including nodebb-plugin-blog-comments. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15156 in the wild and no public exploit code.","fix":"Upgrade nodebb-plugin-blog-comments to 0.7.0 or later.","what":"CVE-2020-15156 is a medium-severity vulnerability in psychobunny nodebb-plugin-blog-comments, published on 26 Aug 2020. 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-2020-15156 and fix it if it is affected.\n\nWhat it is: CVE-2020-15156 is a medium-severity vulnerability in psychobunny nodebb-plugin-blog-comments, published on 26 Aug 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15156 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nodebb-plugin-blog-comments (npm): affected all versions; fixed in 0.7.0\n- nodebb-plugin-blog-comments (npm): affected all versions; fixed in 0.7.0\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-15156/ (Markdown: https://insights.sbomify.com/CVE-2020-15156/index.md)","id":"CVE-2020-15156","markdown":"https://insights.sbomify.com/CVE-2020-15156/index.md","name":"CVE-2020-15156","record":{"aliases":["GHSA-43m5-c88r-cjvv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NodeBB plugin","requires_auth":"none","summary":"A logged-in user can be tricked into posting on their behalf due to missing CSRF validation in the NodeBB blog comments plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"blog_comments","vendor":"nodebb"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"In nodebb-plugin-blog-comments before version 0.7.0, a logged in user is vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum. This is due to lack of CSRF validation.","ecosystems":["npm"],"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":"XSS due to lack of CSRF validation for replying/publishing","id":"CVE-2020-15156","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":2,"n_references":3,"next":{"headline":"containerd can be coerced into leaking credentials during image pull","id":"CVE-2020-15157"},"packages":[{"ecosystem":"npm","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"nodebb-plugin-blog-comments","purl":null,"source":"GHSA-43m5-c88r-cjvv"},{"ecosystem":"npm","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"nodebb-plugin-blog-comments","purl":"pkg:npm/nodebb-plugin-blog-comments","source":"GHSA-43m5-c88r-cjvv"}],"prev":{"headline":"Cross-Site Scripting in baserCMS","id":"CVE-2020-15155"},"products":["nodebb-plugin-blog-comments"],"published":"2020-08-26","related":[],"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":["psychobunny"]},"summary":"A logged-in user can be tricked into posting on their behalf due to missing CSRF validation in the NodeBB blog comments plugin.","url":"https://insights.sbomify.com/CVE-2020-15156/"}