{"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-2025-50979 exists.","fix":"No fix has been published for CVE-2025-50979 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50979 is a high-severity SQL injection vulnerability in n/a, published on 27 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50979 and fix it if it is affected.\n\nWhat it is: CVE-2025-50979 is a high-severity SQL injection vulnerability in n/a, published on 27 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50979 exists.\n\nAffected packages and fixed versions:\n- nodebb (npm): affected all versions up to 4.3.0; no fix listed\n- nodebb (npm): affected all versions up to 4.3.0; 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-2025-50979/ (Markdown: https://insights.sbomify.com/CVE-2025-50979/index.md)","id":"CVE-2025-50979","markdown":"https://insights.sbomify.com/CVE-2025-50979/index.md","name":"CVE-2025-50979","record":{"aliases":["GHSA-rfh2-8vxq-jqr8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NodeBB forum software","requires_auth":"none","summary":"Unauthenticated attackers can inject SQL into the search-categories API to read database contents via blind or error-based techniques.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nodebb","vendor":"nodebb"}],"cvss":{"score":8.6,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"NodeBB v4.3.0 is vulnerable to SQL injection in its search-categories API endpoint (/api/v3/search/categories). The search query parameter is not properly sanitized, allowing unauthenticated, remote attackers to inject boolean-based blind and PostgreSQL error-based payloads.","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":"NodeBB SQL Injection vulnerability","id":"CVE-2025-50979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-50983"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.3.0"],"package":"nodebb","purl":null,"source":"GHSA-rfh2-8vxq-jqr8"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["4.3.0"],"package":"nodebb","purl":"pkg:npm/nodebb","source":"GHSA-rfh2-8vxq-jqr8"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-50978"},"products":["n/a"],"published":"2025-08-27","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-27","vendors":["n/a"]},"summary":"Unauthenticated attackers can inject SQL into the search-categories API to read database contents via blind or error-based techniques.","url":"https://insights.sbomify.com/CVE-2025-50979/"}