# CVE-2022-22690: Umbraco Remote ApplicationURL Overwrite

> Attackers can overwrite the application URL to intercept password reset tokens, leading to account takeover.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jrmq-rv9w-63rv

## What is CVE-2022-22690?

CVE-2022-22690 is a high-severity vulnerability in Umbraco Umbraco Cms, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Within the Umbraco CMS, a configuration element named "UmbracoApplicationUrl" (or just "ApplicationUrl") is used whenever application code needs to build a URL pointing back to the site. For example, when a user resets their password and the application builds a password reset URL or when the administrator invites users to the site. For Umbraco versions less than 9.2.0, if the Application URL is not specifically configured, the attacker can manipulate this value and store it persistently affecting all users for components where the "UmbracoApplicationUrl" is used. For example, the attacker is able to change the URL users receive when resetting their password so that it points to the attackers server, when the user follows this link the reset token can be intercepted by the attacker resulting in account takeover.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

2 open source packages ship an affected version, including Umbraco.Cms.Core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Cms.Core` | NuGet | All versions | 9.2.0 |
| `Umbraco.Cms.Core` | NuGet | All versions | 9.2.0 |

Products: Umbraco Umbraco Cms.

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

Upgrade Umbraco.Cms.Core to 9.2.0 or later.

## Is CVE-2022-22690 being exploited?

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

## Other vulnerabilities in Umbraco Umbraco Cms

- [CVE-2025-67288](https://insights.sbomify.com/CVE-2025-67288/): Umbraco CMS has an arbitrary file upload vulnerability (critical 10.0)
- [CVE-2014-10074](https://insights.sbomify.com/CVE-2014-10074/): File upload in n/a (critical 9.8)
- [CVE-2012-1301](https://insights.sbomify.com/CVE-2012-1301/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2012-10054](https://insights.sbomify.com/CVE-2012-10054/): Umbraco CMS < 4.7.1 codeEditorSave.asmx RCE (critical 9.3)
- [CVE-2025-32017](https://insights.sbomify.com/CVE-2025-32017/): Umbraco has a Management API Vulnerability to Path Traversal With Authenticated Users (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22690 is a high-severity vulnerability in Umbraco Umbraco Cms, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22690 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Cms.Core (NuGet): affected all versions; fixed in 9.2.0
- Umbraco.Cms.Core (NuGet): affected all versions; fixed in 9.2.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-22690/ (Markdown: https://insights.sbomify.com/CVE-2022-22690/index.md)
```

## Sources

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

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