How severe is GHSA-5wrg-8fxp-cx9r?

No CVSS score has been assigned to GHSA-5wrg-8fxp-cx9r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5wrg-8fxp-cx9r?

GHSA-5wrg-8fxp-cx9r affects the following packages: passport-wsfed-saml2 (npm). Ecosystems affected: npm.

How do I fix GHSA-5wrg-8fxp-cx9r?

Update passport-wsfed-saml2 to 3.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wrg-8fxp-cx9r is resolved across your whole dependency graph.

How do I detect GHSA-5wrg-8fxp-cx9r in my npm dependencies?

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

How do I mitigate GHSA-5wrg-8fxp-cx9r 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.

Is GHSA-5wrg-8fxp-cx9r actively exploited in the wild?

No public exploit code has been indexed for GHSA-5wrg-8fxp-cx9r 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-5wrg-8fxp-cx9r published, and has it been updated?

GHSA-5wrg-8fxp-cx9r was published on June 21, 2023. 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

passport-wsfed-saml2 Signature Bypass vulnerabilityGHSA-5wrg-8fxp-cx9r

Fix: auth0/passport-wsfed-saml2#79

GHSA-5wrg-8fxp-cx9r is a security vulnerability in passport-wsfed-saml2. A fix is available for passport-wsfed-saml2 — see the affected versions and patch details below.

Published

Jun 21, 2023

Updated

Jun 21, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 21, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

passport-wsfed-saml2npm

4Kdownloads / week

Description

Information

Please note that this is not a new disclosure, and is previously reported in our SECURITY-NOTICE.md which we removed in favor of github advisory.

Overview

A vulnerability was found in the validation of a SAML signature. The validation doesn't ensure that the "Signature" tag is at the proper location inside an "Assertion" tag. This leads to a signature relocation attack where the attacker can corrupt one field of data while maintaining the signature valid. This could allow an authenticated attacker to "remove" one group from the assertion or corrupt another field of an assertion.

Am I affected?

You are affected if you are using the passport-wsfed-saml2 library to version < 3.0.10

How do I fix it?

You may fix this issue by upgrading passport-wsfed-saml2 library to version 3.0.10 or above.

Will the fix impact my users?

This fix patches the library that your application runs, but will not impact your users, their current state, or any existing sessions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`passport-wsfed-saml2`	all versions	3.0.10`npm install passport-wsfed-saml2@3.0.10`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passport-wsfed-saml2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update passport-wsfed-saml2 to 3.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wrg-8fxp-cx9r 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.

Frequently Asked Questions

## Information Please note that this is not a new disclosure, and is previously reported in our [SECURITY-NOTICE.md](https://github.com/auth0/passport-wsfed-saml2/commit/520b9fc0bb4249ce83bec47e30153419f086ab70 ) which we removed in favor of github advisory. # Overview A vulnerability was found in the validation of a SAML signature. The validation doesn't ensure that the "Signature" tag is at the proper location inside an "Assertion" tag. This leads to a signature relocation attack where the attacker can corrupt one field of data while maintaining the signature valid. This could allow an au

O3 Security · Impact-Aware SCA

Is GHSA-5wrg-8fxp-cx9r in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works