# CVE-2022-29172: HTML injection with additional signup fields

> Attackers can inject HTML into signup fields to execute scripts in verification emails, affecting Auth0 Lock users with additional signup fields enabled.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-7ww6-75fj-jcj7

## What is CVE-2022-29172?

CVE-2022-29172 is a medium-severity cross-site scripting vulnerability in auth0 lock, published on 5 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-29172?

2 open source packages ship an affected version, including auth0-lock. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `auth0-lock` | npm | All versions | 11.33.0 |
| `auth0-lock` | npm | All versions | 11.33.0 |

Products: Auth0 Lock.

## How do I fix CVE-2022-29172?

Upgrade auth0-lock to 11.33.0 or later.

## Is CVE-2022-29172 being exploited?

There is no known exploitation of CVE-2022-29172 in the wild and no public exploit code.

## Other vulnerabilities in auth0 lock

- [CVE-2021-32641](https://insights.sbomify.com/CVE-2021-32641/): Reflected XSS when using flashMessages (high 8.1)
- [CVE-2020-15119](https://insights.sbomify.com/CVE-2020-15119/): DOM-based XSS in auth0-lock (medium 6.4)
- [CVE-2019-20174](https://insights.sbomify.com/CVE-2019-20174/): auth0-lock vulnerable to XSS via unsanitized placeholder property (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29172 and fix it if it is affected.

What it is: CVE-2022-29172 is a medium-severity cross-site scripting vulnerability in auth0 lock, published on 5 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29172 in the wild and no public exploit code.

Affected packages and fixed versions:
- auth0-lock (npm): affected all versions; fixed in 11.33.0
- auth0-lock (npm): affected all versions; fixed in 11.33.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29172/ (Markdown: https://insights.sbomify.com/CVE-2022-29172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29172
- OSV: https://osv.dev/vulnerability/CVE-2022-29172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29172/
Summaries are generated and may contain mistakes; the official description above is the record.