# CVE-2023-36874: Microsoft Windows Error Reporting Service Privilege Escalation

> An attacker can exploit a vulnerability in the Windows Error Reporting Service to elevate privileges on affected Windows systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 11 Jul 2023 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-j95h-qvx8-jp23

## What is CVE-2023-36874?

CVE-2023-36874 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 11 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows Error Reporting Service Elevation of Privilege Vulnerability

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2023-36874?

It affects 12 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

## How do I fix CVE-2023-36874?

No fix has been published for CVE-2023-36874 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 1 Aug 2023.

## Is CVE-2023-36874 being exploited?

Yes. Attackers have exploited CVE-2023-36874 in the wild since at least 11 Jul 2023.

Public exploit code:

- https://github.com/Wh04m1001/CVE-2023-36874 (github_poc): https://github.com/Wh04m1001/CVE-2023-36874
- Weaponized CobaltStrike BOF for CVE-2023-36874 Windows Error Reporting LPE (github_poc): https://github.com/Octoberfest7/CVE-2023-36874_BOF
- This repository contains a proof-of-concept exploit written in C++ that demonstrates the exploitation of a vulnerability affecting the Windows Error Reporting (WER) component. (github_poc): https://github.com/d0rb/CVE-2023-36874
- CVE-2023-36874 Proof of Concept (github_poc): https://github.com/crisprss/CVE-2023-36874
- Microsoft Error Reporting Local Privilege Elevation Vulnerability (metasploit)
- Educational Proof of Concept (PoC) for CVE-2023-36874 — Windows Error Reporting (WER) Local Privilege Escalation vulnerability. (github_poc): https://github.com/johnnygreeme/CVE-2023-36874

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36874 and fix it if it is affected.

What it is: CVE-2023-36874 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 11 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-36874 in the wild since at least 11 Jul 2023.

Affected product: Microsoft Windows 10 1507. 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-2023-36874/ (Markdown: https://insights.sbomify.com/CVE-2023-36874/index.md)
```

## Sources

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

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