# CVE-2022-41040: Microsoft Exchange Server Server-Side Request Forgery

> Attackers can exploit a Server-Side Request Forg flaw in Microsoft Exchange Server to escalate privileges and potentially execute code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 30 Sep 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6ph7-8wxv-6gf2

## What is CVE-2022-41040?

CVE-2022-41040 is a high-severity server-side request forgery vulnerability in Microsoft Exchange Server, published on 3 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microsoft Exchange Server Elevation of Privilege Vulnerability

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Microsoft Exchange Server.

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

No fix has been published for CVE-2022-41040 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Oct 2022.

## Is CVE-2022-41040 being exploited?

Yes. Attackers have exploited CVE-2022-41040 in the wild since at least 30 Sep 2022, including in ransomware campaigns.

Public exploit code:

- CVE-2022-41040 - Server Side Request Forgery (SSRF) in Microsoft Exchange Server (github_poc): https://github.com/kljunowsky/CVE-2022-41040-POC
- the metasploit script(POC) about CVE-2022-41040. Microsoft Exchange are vulnerable to a server-side request forgery (SSRF) attack. An authenticated attacker can use the vulnerability to elevate privileges. (github_poc): https://github.com/TaroballzChen/CVE-2022-41040-metasploit-ProxyNotShell
- CVE-2022-41040 nuclei template (github_poc): https://github.com/numanturle/CVE-2022-41040
- mitigation script for MS Exchange server vuln (github_poc): https://github.com/r3dcl1ff/CVE-2022-41040
- Code set relating to CVE-2022-41040 (github_poc): https://github.com/d3duct1v/CVE-2022-41040
- Script to check for IOC's created by ProxyNotShell (CVE-2022-41040 & CVE-2022-41082) (github_poc): https://github.com/rjsudlow/proxynotshell-IOC-Checker

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41040 is a high-severity server-side request forgery vulnerability in Microsoft Exchange Server, published on 3 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-41040 in the wild since at least 30 Sep 2022, including in ransomware campaigns.

Affected product: Microsoft Exchange Server. 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-41040/ (Markdown: https://insights.sbomify.com/CVE-2022-41040/index.md)
```

## Sources

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

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