Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-43m5-c88r-cjvv is a medium-severity (CVSS 6.8) Cross-Site Request Forgery (CSRF) vulnerability in nodebb-plugin-blog-comments. O3 Security confirms whether GHSA-43m5-c88r-cjvv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XSS due to lack of CSRF validation for replying/publishing

Also known asCVE-2020-15156
Published
Aug 26, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦nodebb-plugin-blog-comments

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Due to lack of CSRF validation, a logged in user is potentially vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum.

Patches

Upgrade to the latest version v0.7.0

Workarounds

You can cherry-pick the following commit: https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618

References

Visit https://community.nodebb.org if you have any questions about this issue or on how to patch / upgrade your instance.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnodebb-plugin-blog-commentsall versions0.7.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nodebb-plugin-blog-comments. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update nodebb-plugin-blog-comments to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-43m5-c88r-cjvv is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-43m5-c88r-cjvv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-43m5-c88r-cjvv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Due to lack of CSRF validation, a logged in user is potentially vulnerable to an XSS attack which could allow a third party to post on their behalf on the forum. ### Patches Upgrade to the latest version v0.7.0 ### Workarounds You can cherry-pick the following commit: [https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618](https://github.com/psychobunny/nodebb-plugin-blog-comments/commit/cf43beedb05131937ef46f365ab0a0c6fa6ac618) ### References Visit https://community.nodebb.org if you have any questions about this issue or on h
O3 Security · Impact-Aware SCA

Is GHSA-43m5-c88r-cjvv in your dependencies?

O3 detects GHSA-43m5-c88r-cjvv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-43m5-c88r-cjvv: XSS due to lack of… | O3 Security