CVE-2025-49706 — Microsoft SharePoint Improper Authentication Vulnerability
Improper authentication in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Used in ransomware campaigns (CISA)+10
- Public exploit/PoC (nuclei, metasploit, github)+20
- EPSS 99.1% (30-day exploitation probability)+15
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
CISA required action CISA
Disconnect public-facing versions of SharePoint Server that have reached their end-of-life (EOL) or end-of-service (EOS) to include SharePoint Server 2013 and earlier versions. For supported versions, please follow the mitigations according to CISA (URL listed below in Notes) and vendor instructions (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available.
US federal deadline: Jul 23, 2025 — passed 449 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft Microsoft SharePoint Server 2019, Microsoft Microsoft SharePoint Server Subscription Edition…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | Microsoft SharePoint Enterprise Server 2016 | ≥ 16.0.0 and < 16.0.5508.1000 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft SharePoint Server 2019 | ≥ 16.0.0 and < 16.0.10417.20027 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Microsoft SharePoint Server Subscription Edition | ≥ 16.0.0 and < 16.0.18526.20424 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Sharepoint Enterprise Server | version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Sharepoint Server | < 16.0.18526.20424version 2019 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | Medium | 3.9 | 2.5 | secure@microsoft.com via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | microsoft via CVE Program (cve.org) e CISA ADP |
| 6.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: secure@microsoft.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 99.10%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
- Hunt retroactively in logs from before Jul 22, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · microsoft/microsoft sharepoint enterprise server 2016, microsoft/microsoft sharepoint server 2019, microsoft/microsoft s
- SSVC assessment updated
- Record published
- Affected products added · microsoft/sharepoint enterprise server, microsoft/sharepoint server
- CVSS changed · 6.5
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- www.microsoft.com/en-us/security/blog/2025/07/22/disrupting-active-exploitation-of-on-p
- msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49706
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- nvd.nist.gov/vuln/detail/CVE-2025-49706
- www.microsoft.com/en-us/security/blog/2025/07/22/disrupting-active-exploitation-of-on-p
- github.com/advisories/GHSA-j67g-r75f-8hgp
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-108452 Microsoft Office SharePoint Remote Code Execution Vulnerability 34m
- High CVE-2026-88164 Microsoft Office SharePoint Elevation of Privilege Vulnerability 1d
- Medium CVE-2026-97782 Microsoft Office SharePoint Tampering Vulnerability 2d
- Medium CVE-2026-97783 Microsoft Office SharePoint Spoofing Vulnerability 2d
- High CVE-2026-97755 Microsoft Office Excel Remote Code Execution Vulnerability 2d
- High CVE-2026-96044 Microsoft Office SharePoint Elevation of Privilege Vulnerability 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-49706 is "Microsoft SharePoint Improper Authentication Vulnerability", rated Medium. It affects Microsoft SharePoint Enterprise Server 2016 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 6.5 describes technical severity. EPSS 99.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.