Reflected XSS when using flashMessages or languageDictionaryGHSA-jr3j-whm4-9wwm
HIGHFix: auth0/lock@d139cf0GHSA-jr3j-whm4-9wwm is a high-severity (CVSS 8.1) Cross-site Scripting (XSS) vulnerability in auth0-lock. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for auth0-lock — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
auth0-locknpmDescription
Overview
Versions before and including 11.30.0 are vulnerable to reflected XSS. An attacker can execute arbitrary code when the library's
flashMessagefeature is utilized and user input or data from URL parameters is incorporated into theflashMessage.languageDictionaryfeature is utilized and user input or data from URL parameters is incorporated into thelanguageDictionary.
Am I affected?
You are affected by this vulnerability if you are using auth0-lock version 11.30.0 or lower and all of the following conditions apply:
- You are utilizing
flashMessagefeature. - User input or data from URL parameters is incorporated into the
flashMessage.
An example of a vulnerable snippet where query parameters are used to populate the text property of a flashMessage.
var params = new URLSearchParams(location.search);
var errorMessage = params.get('error__message');
var showParams = {};
if (!!errorMessage === true) {
showParams.flashMessage = {
type: 'error',
text: 'We were unable to log you in. ' + errorMessage,
};
}
lock.show(showParams);
OR
- You are utilizing
languageDictionaryfeature. - User input or data from URL parameters is used in
languageDictionaryproperties.
An example of a vulnerable snippet where query parameters are used to populate the socialLoginInstructions property of a languageDictionary.
var params = new URLSearchParams(location.search);
var instruction = params.get('instruction');
var options = {
languageDictionary: {
emailInputPlaceholder: "[email protected]",
title: "title",
socialLoginInstructions: instruction
},
};
var lock = new Auth0LockPasswordless(
CLIENT_ID,
DOMAIN,
options
);
lock.show()
How to fix that?
Upgrade to version 11.30.1.
Will this update impact my users?
The fix uses DOMPurify to sanitise the flashMessage and languageDictionary inputs. If you are including inline JavaScript in these fields, like script tags or onclick attributes, these will be removed.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | auth0-lock | all versions | 11.30.1npm install auth0-lock@11.30.1 |
Affected Products
lockauth0Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for auth0-lock, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update auth0-lock to 11.30.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jr3j-whm4-9wwm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-jr3j-whm4-9wwm in your dependencies?
Find it across npm, including transitive dependencies.