# CVE-2025-49706: Microsoft SharePoint Improper Authentication

> An unauthorized attacker can perform spoofing attacks against Microsoft SharePoint Server due to improper authentication mechanisms.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 22 Jul 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-j67g-r75f-8hgp

## What is CVE-2025-49706?

CVE-2025-49706 is a medium-severity authentication bypass vulnerability in Microsoft Sharepoint Enterprise Server, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper authentication in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-49706?

It affects 2 products.


Products: Microsoft Sharepoint Enterprise Server, Microsoft Sharepoint Server.

## How do I fix CVE-2025-49706?

No fix has been published for CVE-2025-49706 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Jul 2025.

## Is CVE-2025-49706 being exploited?

Yes. Attackers have exploited CVE-2025-49706 in the wild since at least 22 Jul 2025, including in ransomware campaigns.

Public exploit code:

- A deep dive into CVE-2025-49706 — the SharePoint spoofing flaw now exploited in the wild for stealthy web shell deployment and privilege escalation. (github_poc): https://github.com/AdityaBhatt3010/CVE-2025-49706-SharePoint-Spoofing-Vulnerability-Under-Active-Exploitation
- Microsoft SharePoint Server ToolPane Unauthenticated Remote Code Execution (aka ToolShell) (metasploit)
- Microsoft SharePoint Server - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-49706.yaml

## Other vulnerabilities in Microsoft Sharepoint Enterprise Server

- [CVE-2019-0604](https://insights.sbomify.com/CVE-2019-0604/): Microsoft SharePoint Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-24955](https://insights.sbomify.com/CVE-2023-24955/): Microsoft SharePoint Server Code Injection (high 7.2, exploited in the wild)
- [CVE-2020-1210](https://insights.sbomify.com/CVE-2020-1210/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2020-1595](https://insights.sbomify.com/CVE-2020-1595/): Microsoft SharePoint Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2025-47163](https://insights.sbomify.com/CVE-2025-47163/): Microsoft SharePoint Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49706 and fix it if it is affected.

What it is: CVE-2025-49706 is a medium-severity authentication bypass vulnerability in Microsoft Sharepoint Enterprise Server, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-49706 in the wild since at least 22 Jul 2025, including in ransomware campaigns.

Affected product: Microsoft Sharepoint Enterprise 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-2025-49706/ (Markdown: https://insights.sbomify.com/CVE-2025-49706/index.md)
```

## Sources

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

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