CVE-2020-5263: Information disclosure through error object in auth0.js

auth0-js Updated 02 Oct 2025

Summary

10/04/2020
Yes i
High
5.5

CVE-2020-5263: Information disclosure through error object in auth0.js. Affects auth0-js versions >= 8.0.0, < 9.13.2. Fixed in 9.13.2. 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 Penetration testing for web, API and mobile 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 a JavaScript library provided by Auth0 that allows developers to easily integrate authentication and authorization into their applications. It provides a set of functions and methods for handling user authentication and managing user sessions. This vulnerability affects versions 8.0.0 to 9.13.1 (inclusive) of the auth0.js library. The vulnerability arises when an authentication error occurs, and the error object returned by the library contains the original request of the user, which may include the plaintext password entered by the user. If this error object is exposed or logged without modification, it can lead to the exposure of user passwords.

Vulnerability Detail

The vulnerability in auth0.js versions 8.0.0 to 9.13.1 allows for information disclosure. When an authentication error occurs, the error object returned by the library includes the original user request, which may contain the plaintext password. If this error object is not properly filtered or modified before being stored or displayed, it can result in the exposure of user passwords. This can have serious ramifications, as it compromises the security and privacy of user accounts. The vulnerability has a CVSS score of 5.5, indicating a moderate severity level.

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.13.2

This is the first release that contains the fix.

npm install auth0-js@9.13.2

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

Workaround

A temporary workaround for this vulnerability is to avoid storing or displaying the error object publicly without modification. By filtering or removing the sensitive information, such as the plaintext password, from the error object, the risk of password exposure can be reduced. However, it is important to note that this is not a permanent solution and upgrading to a fixed version of auth0.js is highly recommended.

Conclusion

In conclusion, the vulnerability in auth0.js versions 8.0.0 to 9.13.1 allows for the exposure of user passwords through the error object. To mitigate this vulnerability, it is recommended to upgrade to auth0.js version 9.13.2 or later, where user inputted passwords are masked in errors. If immediate upgrading is not possible, developers should avoid storing or publicly displaying the error object without modification. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for auth0-js →

Share this vulnerability

FAQ

You are affected by this vulnerability if you are using auth0.js version between 8.0.0 and 9.13.1 (inclusive) and you store or display error objects without filtering.

To fix this vulnerability, you should upgrade to auth0.js version 9.13.2 or later. This version masks user inputted passwords in errors, preventing their exposure.

The potential consequences of this vulnerability include the exposure of user passwords. This can lead to unauthorized access to user accounts and compromise the security and privacy of users.

A temporary fix for this vulnerability is to avoid storing or publicly displaying the error object without modification. By filtering or removing sensitive information, such as the plaintext password, the risk of password exposure can be mitigated.

Upgrading to a fixed version of auth0.js may require changes in application code due to the password no longer being available in the error object. However, it will not impact your users, their current state, or any existing sessions.

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.13.2

This is the first release that contains the fix.

npm install auth0-js@9.13.2

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