How severe is GHSA-5wmg-9cvh-qw25?

No CVSS score has been assigned to GHSA-5wmg-9cvh-qw25 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5wmg-9cvh-qw25?

GHSA-5wmg-9cvh-qw25 affects the following packages: @workos-inc/authkit-nextjs (npm). Ecosystems affected: npm.

How do I fix GHSA-5wmg-9cvh-qw25?

Update @workos-inc/authkit-nextjs to 0.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wmg-9cvh-qw25 is resolved across your whole dependency graph.

How do I detect GHSA-5wmg-9cvh-qw25 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @workos-inc/authkit-nextjs. 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.

How do I mitigate GHSA-5wmg-9cvh-qw25 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-5wmg-9cvh-qw25?

O3 pinpoints whether GHSA-5wmg-9cvh-qw25 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5wmg-9cvh-qw25 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5wmg-9cvh-qw25 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.

What is the EPSS score for GHSA-5wmg-9cvh-qw25?

GHSA-5wmg-9cvh-qw25 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5wmg-9cvh-qw25?

GHSA-5wmg-9cvh-qw25 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5wmg-9cvh-qw25 published, and has it been updated?

GHSA-5wmg-9cvh-qw25 was published on November 5, 2024 and was last updated on November 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-5wmg-9cvh-qw25

@workos-inc/authkit-nextjs refresh tokens are logged when the debug flag is enabled

Also known asCVE-2024-51752

Published

Nov 5, 2024

Updated

Nov 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk16th percentile+0.07%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@workos-inc/authkit-nextjsnpm

399Kdownloads / week

Description

Impact

Refresh tokens are logged to the console when the disabled by default debug flag, is enabled.

Patches

Patched in https://github.com/workos/authkit-nextjs/releases/tag/v0.13.2

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@workos-inc/authkit-nextjs`	all versions	0.13.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @workos-inc/authkit-nextjs. 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.
Fix
Update @workos-inc/authkit-nextjs to 0.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wmg-9cvh-qw25 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-5wmg-9cvh-qw25 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-5wmg-9cvh-qw25. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Refresh tokens are logged to the console when the disabled by default `debug` flag, is enabled. ### Patches Patched in [https://github.com/workos/authkit-nextjs/releases/tag/v0.13.2](https://github.com/workos/authkit-nextjs/releases/tag/v0.13.2)

O3 Security · Impact-Aware SCA

Is GHSA-5wmg-9cvh-qw25 in your dependencies?

O3 detects GHSA-5wmg-9cvh-qw25 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works