CVE-2020-15119

CVE-2020-15119 is a low-severity cross-site scripting (XSS) vulnerability in auth0-lock (npm), affecting versions <= 11.25.1. It is fixed in 11.26.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

DOM-based XSS in auth0-lock

Overview

Versions before and including 11.25.1 are using dangerouslySetInnerHTML to display an informational message when used with a Passwordless or Enterprise connection.

  • For Passwordless connection, the value of the input (email or phone number) is displayed back to the user while waiting for verification code input.
  • For Enterprise connection, the value of the input (IdP Domain) from the Enterprise connection setup screen (Auth0 Dashboard) is displayed back to the user when the lock widget opens.

When Passwordless or Enterprise connection is used, the application and its users might be exposed to cross-site scripting (XSS) attacks.

Am I affected?

You are affected by this vulnerability if all of the following conditions apply:

  • You are using auth0-lock
  • You are using Passwordless or Enterprise connection mode

How to fix that?

Upgrade to version 11.26.3

Will this update impact my users?

The fix provided in patch will not affect your users.

Credit

https://github.com/mvisat

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2020-15119 has a CVSS score of 6.4 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.26.3); upgrading removes the vulnerable code path.

Affected versions

auth0-lock (<= 11.25.1)

Security releases

auth0-lock → 11.26.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade auth0-lock to 11.26.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2020-15119? CVE-2020-15119 is a low-severity cross-site scripting (XSS) vulnerability in auth0-lock (npm), affecting versions <= 11.25.1. It is fixed in 11.26.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. How severe is CVE-2020-15119? CVE-2020-15119 has a CVSS score of 6.4 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of auth0-lock are affected by CVE-2020-15119? auth0-lock (npm) versions <= 11.25.1 is affected.
  4. Is there a fix for CVE-2020-15119? Yes. CVE-2020-15119 is fixed in 11.26.3. Upgrade to this version or later.
  5. Is CVE-2020-15119 exploitable, and should I be worried? Whether CVE-2020-15119 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2020-15119 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2020-15119? Upgrade auth0-lock to 11.26.3 or later.

Other vulnerabilities in auth0-lock

Stop the waste.
Protect your environment with Kodem.