{"answers":{"affected":"2 open source packages ship an affected version, including nodebb. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36076 exists.","fix":"Upgrade nodebb to 1.17.2 or later.","what":"CVE-2022-36076 is a high-severity vulnerability in NodeBB, published on 2 Sep 2022. 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-2022-36076 and fix it if it is affected.\n\nWhat it is: CVE-2022-36076 is a high-severity vulnerability in NodeBB, published on 2 Sep 2022. 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-2022-36076 exists.\n\nAffected packages and fixed versions:\n- nodebb (npm): affected all versions; fixed in 1.17.2\n- nodebb (npm): affected all versions; fixed in 1.17.2\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-2022-36076/ (Markdown: https://insights.sbomify.com/CVE-2022-36076/index.md)","id":"CVE-2022-36076","markdown":"https://insights.sbomify.com/CVE-2022-36076/index.md","name":"CVE-2022-36076","record":{"aliases":["GHSA-xmgg-fx9p-prq6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"NodeBB forum software","requires_auth":"none","summary":"Attackers can take over user accounts via MITM attacks during SSO due to missing nonce checks in NodeBB forum software.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nodebb","vendor":"nodebb"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. Due to an unnecessarily strict conditional in the code handling the first step of the SSO process, the pre-existing logic that added (and later checked) a nonce was inadvertently rendered opt-in instead of opt-out. This re-exposed a vulnerability in that a specially crafted Man-in-the-Middle (MITM) attack could theoretically take over another user account during the single sign-on process. The issue has been fully patched in version 1.17.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Account takeover via SSO plugins in NodeBB","id":"CVE-2022-36076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":2,"n_references":3,"next":{"headline":"Electron subject to Exfiltration of hashed SMB credentials on Windows via file:// redirect","id":"CVE-2022-36077"},"packages":[{"ecosystem":"npm","fixed":["1.17.2"],"introduced":["0"],"last_affected":[],"package":"nodebb","purl":null,"source":"GHSA-xmgg-fx9p-prq6"},{"ecosystem":"npm","fixed":["1.17.2"],"introduced":["0"],"last_affected":[],"package":"nodebb","purl":"pkg:npm/nodebb","source":"GHSA-xmgg-fx9p-prq6"}],"prev":{"headline":"File list exposure in Nextcloud Files Access Control","id":"CVE-2022-36075"},"products":["NodeBB"],"published":"2022-09-02","related":[{"cvss_score":10,"headline":"NodeBB vulnerable to path traversal and code execution via prototype vulnerability","id":"CVE-2023-26045","kev_date_added":null,"published":"2023-07-24"},{"cvss_score":9.9,"headline":"Account takeover in NodeBB","id":"CVE-2020-15149","kev_date_added":null,"published":"2020-08-19"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-43187","kev_date_added":null,"published":"2023-09-26"},{"cvss_score":9.8,"headline":"API token verification can be bypassed","id":"CVE-2021-43786","kev_date_added":null,"published":"2021-11-29"},{"cvss_score":9.4,"headline":"Account takeover via prototype vulnerability","id":"CVE-2022-46164","kev_date_added":null,"published":"2022-12-05"},{"cvss_score":9,"headline":"Account takeover via cryptographically weak PRNG in NodeBB Forum","id":"CVE-2022-36045","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":9,"headline":"XSS via prototype pollution","id":"CVE-2021-43787","kev_date_added":null,"published":"2021-11-29"}],"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":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["NodeBB"]},"summary":"Attackers can take over user accounts via MITM attacks during SSO due to missing nonce checks in NodeBB forum software.","url":"https://insights.sbomify.com/CVE-2022-36076/"}