HTML injection with additional signup fields
Auth0 is an authentication broker that supports both social and enterprise identity providers, including Active Directory, LDAP, Google Apps, and Salesforce. In versions before `11.33.0`, when the “additional signup fields” feature [is configured](https://github.com/auth0/lock#additional-sign-up-fields), a malicious actor can inject invalidated HTML code into these additional fields, which is then stored in the service `user_metdata` payload (using the `name` property). Verification emails, when applicable, are generated using this metadata. It is therefor possible for an actor to craft a malicious link by injecting HTML, which is then rendered as the recipient's name within the delivered email template. You are impacted by this vulnerability if you are using `auth0-lock` version `11.32.2` or lower and are using the “additional signup fields” feature in your application. Upgrade to version `11.33.0`.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-29172
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 19:14 UTC · Revision 1
Source evidence
HTML injection with additional signup fields
core-osv · Original sourcePublished 5 May 2022, 22:50 UTC
Auth0 is an authentication broker that supports both social and enterprise identity providers, including Active Directory, LDAP, Google Apps, and Salesforce. In versions before `11.33.0`, when the “additional signup fields” feature [is configured](https://github.com/auth0/lock#additional-sign-up-fields), a malicious actor can inject invalidated HTML code into these additional fields, which is then stored in the service `user_metdata` payload (using the `name` property). Verification emails, when applicable, are generated using this metadata. It is therefor possible for an actor to craft a malicious link by injecting HTML, which is then rendered as the recipient's name within the delivered email template. You are impacted by this vulnerability if you are using `auth0-lock` version `11.32.2` or lower and are using the “additional signup fields” feature in your application. Upgrade to version `11.33.0`.
osv:CVE-2022-29172
Complete source record
{
"id": "d845f7dec62082f0db94eb096207e522e97685288ad44de1dfd5fa86599cec09",
"url": "https://osv.dev/vulnerability/CVE-2022-29172",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "HTML injection with additional signup fields",
"summary": "Auth0 is an authentication broker that supports both social and enterprise identity providers, including Active Directory, LDAP, Google Apps, and Salesforce. In versions before `11.33.0`, when the “additional signup fields” feature [is configured](https://github.com/auth0/lock#additional-sign-up-fields), a malicious actor can inject invalidated HTML code into these additional fields, which is then stored in the service `user_metdata` payload (using the `name` property). Verification emails, when applicable, are generated using this metadata. It is therefor possible for an actor to craft a malicious link by injecting HTML, which is then rendered as the recipient's name within the delivered email template. You are impacted by this vulnerability if you are using `auth0-lock` version `11.32.2` or lower and are using the “additional signup fields” feature in your application. Upgrade to version `11.33.0`.",
"evidence": "osv:CVE-2022-29172",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2022-29172",
"aliases": [
"CVE-2022-29172",
"GHSA-7ww6-75fj-jcj7"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/auth0/lock",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "49e517d477246cee2c69cb05b03fdf602f062612"
},
{
"fixed": "79ae557d331274b114848150f19832ae341771b1"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:auth0:lock:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "11.33.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "79ae557d331274b114848150f19832ae341771b1"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v11.32.2",
"v11.32.1",
"v11.32.0",
"v11.31.1",
"v11.31.0",
"v11.30.6",
"v11.30.5",
"v11.28.1",
"v11.26.1",
"v11.22.4"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-29172.json"
}
}
],
"modified": "2026-10-28T02:30:38.588070324Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/29xxx/CVE-2022-29172.json",
"https://github.com/auth0/lock/security/advisories/GHSA-7ww6-75fj-jcj7",
"https://nvd.nist.gov/vuln/detail/CVE-2022-29172",
"https://github.com/auth0/lock/commit/79ae557d331274b114848150f19832ae341771b1"
],
"provider_metadata": {
"cwe_ids": [
"CWE-79"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/29xxx/CVE-2022-29172.json"
}
},
"related_cves": [
{
"value": "CVE-2022-29172",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 506054,
"published_at": "2022-05-05T22:50:09+00:00"
}