CVE-2025-49706
Improper authentication in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network.
do firstDisconnect 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.
Can a WAF block it? No. Authentication bypass is a flaw in the application's logic. The attack requests look like normal traffic, so a WAF has nothing to match on.
Also consider: patch · add auth middleware
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-49706 being exploited?
Yes. CVE-2025-49706 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-49706?
CVE-2025-49706 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-49706?
Yes. A fix has been recorded for CVE-2025-49706. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-49706 affect?
CVE-2025-49706 affects microsoft:sharepoint_enterprise_server, microsoft:sharepoint_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 16.0.0 and < 16.0.5508.1000
- affected>= 16.0.0 and < 16.0.10417.20027
- affected>= 16.0.0 and < 16.0.18526.20424
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 Metasploit module · 1 GitHub proof of concept · 1 Nuclei template
- exploit/windows/http/sharepoint_toolpane_rce · exploit · excellent
- Microsoft SharePoint Server - Authentication Bypass · detection template · medium
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 22 Jul 2025 (SSVC 2.0.3).
timeline
- 8 Jul 2025Published
- 20 Jul 2025First public exploit or proof of concept · 11 days later
- 22 Jul 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 22 Jul 2025CISA SSVC assessment: exploitation active · same day later
- 23 Jul 2025CISA remediation due date (US federal agencies) · 1 day later
- 4 Aug 2026CVE record last updated · 377 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
- Advisorymicrosoft.com /en-us/security/blog/2025/07/22/disrupting-active-exploitation-of-on-premises-sh
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-49706
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-49706
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.