# CVE-2023-36769: Microsoft OneNote Spoofing Vulnerability


- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2023
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-j6h3-42q7-8pjm

## What is CVE-2023-36769?

CVE-2023-36769 is a medium-severity vulnerability in Microsoft Office 2019, published on 6 Nov 2023. 

### Official description

Microsoft OneNote Spoofing Vulnerability

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Microsoft Onenote.

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

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

## Is CVE-2023-36769 being exploited?

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

## Other vulnerabilities in Microsoft Office 2019

- [CVE-2014-2815](https://insights.sbomify.com/CVE-2014-2815/): Code injection in n/a (high 8.8)
- [CVE-2017-0197](https://insights.sbomify.com/CVE-2017-0197/): Code injection in Office (high 7.8)
- [CVE-2024-41159](https://insights.sbomify.com/CVE-2024-41159/): Privilege escalation in OneNote (high 7.1)
- [CVE-2023-33140](https://insights.sbomify.com/CVE-2023-33140/): Microsoft OneNote Spoofing Vulnerability (medium 6.5)
- [CVE-2023-21721](https://insights.sbomify.com/CVE-2023-21721/): Microsoft OneNote Elevation of Privilege Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36769 is a medium-severity vulnerability in Microsoft Office 2019, published on 6 Nov 2023. 
Exploitation: There is no known exploitation of CVE-2023-36769 in the wild and no public exploit code.

Affected product: Microsoft Office 2019. 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-36769/ (Markdown: https://insights.sbomify.com/CVE-2023-36769/index.md)
```

## Sources

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

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