CVE-2018-7307: Auth0-js bypasses CSRF checks

auth0-js Updated 02 Oct 2025

Summary

07/03/2018
Yes i
High
8.8

CVE-2018-7307: Auth0-js bypasses CSRF checks. Affects auth0-js versions < 9.3.0. Fixed in 9.3.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Auth0-js is an npm package that provides authentication and authorization services for web applications. It is widely used to implement user authentication and authorization in JavaScript-based applications. The package allows developers to integrate their applications with Auth0, a popular identity management platform. However, versions below 9.3 of Auth0-js are vulnerable to a CSRF (Cross-Site Request Forgery) bypass. This vulnerability can be exploited by an attacker to bypass the CSRF check from the state parameter if it's missing from the authorization response. As a result, the client becomes vulnerable to CSRF attacks, which can lead to unauthorized access, data leakage, and other security breaches.

Vulnerability Detail

The vulnerability in Auth0-js versions below 9.3 allows an attacker to bypass the CSRF check from the state parameter. This check is an important security measure to prevent CSRF attacks, which involve tricking a user into performing unintended actions on a web application. By bypassing this check, an attacker can forge requests on behalf of the user, potentially leading to unauthorized actions, data theft, or other malicious activities. The vulnerability originates from a missing state parameter in the authorization response, which should be validated to ensure the authenticity of the request. The impact of this vulnerability is significant, as it exposes applications using vulnerable versions of Auth0-js to potential CSRF attacks.

How To Fix

Latest published version: 10.3.0 as of 22 Oct 2026

npm install auth0-js@10.3.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

9.3.0

This is the first release that contains the fix.

npm install auth0-js@9.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the latest secure version of Auth0-js.

Conclusion

The vulnerability in Auth0-js versions below 9.3 allows an attacker to bypass CSRF checks, potentially leading to unauthorized actions and data breaches. To mitigate this vulnerability, it is crucial to upgrade to Auth0-js version 9.3.0 or above. Developers should follow the recommended steps provided by Auth0 and thoroughly test the application after the upgrade. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for auth0-js →

Share this vulnerability

FAQ

CSRF (Cross-Site Request Forgery) is an attack that tricks the victim into submitting a malicious request. It occurs when a malicious website or application forces a user's browser to perform unwanted actions on a trusted website where the user is authenticated.

CSRF attacks can lead to unauthorized actions, data leakage, account hijacking, and other security breaches. Attackers can perform actions on behalf of the victim, such as changing passwords, making unauthorized purchases, or accessing sensitive information.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the package-lock.json file.

There are no known public exploits for this vulnerability at the time of writing. However, it is important to promptly upgrade to the latest secure version to mitigate the risk.

You can find more information about this vulnerability, including its fix, in the GitHub advisory database (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/03/GHSA-wpq7-q8j4-72jg/GHSA-wpq7-q8j4-72jg.json). It is recommended to follow the official documentation and release notes provided by Auth0 for a comprehensive understanding of the vulnerability and its resolution.

Related vulnerabilities

Recent vulnerabilities recorded for auth0-js.

How To Fix

Latest published version: 10.3.0 as of 22 Oct 2026

npm install auth0-js@10.3.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

9.3.0

This is the first release that contains the fix.

npm install auth0-js@9.3.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback