# CVE-2022-21891: Microsoft Dynamics 365 (on-premises) Spoofing Vulnerability

> An attacker can spoof information in Microsoft Dynamics 365 Sales, potentially misleading users or bypassing security controls.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jan 2022
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-m9fv-32mm-97pv

## What is CVE-2022-21891?

CVE-2022-21891 is a high-severity vulnerability in Microsoft Dynamics 365 Sales, published on 11 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Microsoft Dynamics 365 (on-premises) Spoofing Vulnerability

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

It affects 1 product.


Products: Microsoft Dynamics 365 Sales.

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

No fix has been published for CVE-2022-21891 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-21891 being exploited?

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

## Other vulnerabilities in Microsoft Dynamics 365 Sales

- [CVE-2025-21177](https://insights.sbomify.com/CVE-2025-21177/): Microsoft Dynamics 365 Sales Elevation of Privilege Vulnerability (high 8.7)
- [CVE-2024-49053](https://insights.sbomify.com/CVE-2024-49053/): Microsoft Dynamics 365 Sales Spoofing Vulnerability (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21891 is a high-severity vulnerability in Microsoft Dynamics 365 Sales, published on 11 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-21891 in the wild and no public exploit code.

Affected product: Microsoft Dynamics 365 Sales. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-21891/ (Markdown: https://insights.sbomify.com/CVE-2022-21891/index.md)
```

## Sources

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

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