How severe is GHSA-8wgc-jjvv-cv6v?

No CVSS score has been assigned to GHSA-8wgc-jjvv-cv6v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8wgc-jjvv-cv6v?

GHSA-8wgc-jjvv-cv6v affects the following packages: loopback (npm), loopback (npm). Ecosystems affected: npm.

How do I fix GHSA-8wgc-jjvv-cv6v?

Update loopback to 2.40.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wgc-jjvv-cv6v is resolved across your whole dependency graph.

How do I detect GHSA-8wgc-jjvv-cv6v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8wgc-jjvv-cv6v if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-8wgc-jjvv-cv6v actively exploited in the wild?

No public exploit code has been indexed for GHSA-8wgc-jjvv-cv6v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8wgc-jjvv-cv6v published, and has it been updated?

GHSA-8wgc-jjvv-cv6v was published on September 2, 2020 and was last updated on September 27, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Improper Authorization in loopbackGHSA-8wgc-jjvv-cv6v

GHSA-8wgc-jjvv-cv6v is a security vulnerability in loopback. A fix is available for loopback — see the affected versions and patch details below.

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 27, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

256other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

loopbacknpm

36Kdownloads / week

Description

Vulnerable versions of loopback may allow attackers to create Authentication Tokens on behalf of other users due to Improper Authorization. If the AccessToken model is publicly exposed, an attacker can create Authorization Tokens for any user as long as they know the target's userId. This will allow the attacker to access the user's data and their privileges.

Recommendation

For loopback 2.x, upgrade to version 2.40.0 or later For loopback 3.x, upgrade to version 3.22.0 or later

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`loopback`	all versions	2.40.0`npm install loopback@2.40.0`
📦npm	`loopback`	≥ 3.0.0&&< 3.22.0	3.22.0`npm install loopback@3.22.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loopback to 2.40.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wgc-jjvv-cv6v is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Vulnerable versions of `loopback` may allow attackers to create Authentication Tokens on behalf of other users due to Improper Authorization. If the AccessToken model is publicly exposed, an attacker can create Authorization Tokens for any user as long as they know the target's `userId`. This will allow the attacker to access the user's data and their privileges. ## Recommendation For loopback 2.x, upgrade to version 2.40.0 or later For loopback 3.x, upgrade to version 3.22.0 or later

O3 Security · Impact-Aware SCA

Is GHSA-8wgc-jjvv-cv6v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works