VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

nodebb: vulnerability history, versions and safety

nodebb is a package in the npm ecosystem. Vulert records 14 vulnerabilities for it across 6 releases, from May 2019 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C5 H2 M7
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nodebb vulnerabilities

Vulert verdict on nodebb 1.4.0 i

Updated on 23 Oct 2026

Careful: 1.4.0 has 8 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 59/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.4.0 — affected i
  • Vulnerabilities on record 14 over 6 years · 0 in the last year i
  • Latest disclosure 27 Aug 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 1 i
  • Stars 15,240 i
  • OpenSSF scorecard 5/10 i
  • Last release 118 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for nodebb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.4.0 12 Dec 2016 C2 H2 M4 GPL-3.0 No Details →
0.8.2 25 Sep 2015 C2 H2 M4 GPL-3.0 No Details →
0.7.0 24 May 2015 C2 H2 M5 non-standard No Details →
0.6.1 07 Feb 2015 C2 H2 M5 non-standard No Details →
0.6.1-dev 23 Jan 2015 C2 H2 M5 non-standard No Details →
0.4.3 24 Jun 2014 C2 H2 M5 non-standard No Details →

All 6 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 3
  • 2022 5
  • 2023 2
  • 2024 1
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for nodebb

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-26045: Path traversal and code execution in nodebb 10.0 critical 2.8.7 25 Jul 2023
CVE-2021-43786: API token verification bypass in NodeBB 9.8 critical 1.18.5 30 Nov 2021
CVE-2022-36045: Cryptographically weak PRNG in NodeBB 9.8 critical 1.19.8 30 Aug 2022
CVE-2022-46164: NodeBB Account Takeover via Prototype Vulnerability 9.4 critical 2.6.1 05 Dec 2022
CVE-2021-43787: XSS via prototype pollution in NodeBB 9.0 critical 1.18.5 30 Nov 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About nodebb

Is nodebb safe to use?

Vulert records 14 vulnerabilities for nodebb in npm: 5 critical, 2 high, 7 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is nodebb's Vulert package health score?

Vulert scores nodebb 59/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of nodebb affected?

Yes. 1.4.0, the version you would install today, has 8 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does nodebb have?

14 vulnerabilities are recorded for nodebb in the npm ecosystem: 5 critical, 2 high, 7 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nodebb vulnerabilities disclosed?

0 vulnerabilities were recorded for nodebb in the last 12 months, and the oldest entry in this database dates to 01 May 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of nodebb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor nodebb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the nodebb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.