Vulnerability report

Trusted Third Party Report Confirmed Confidence In CISA KEV

CVE-2025-49704

Microsoft SharePoint Remote Code Execution Vulnerability

Microsoft SharePoint Enterprise Server 2016 · affected before 16.0.5508.1000

Watch CVE-2025-49704 Browse KEV feed
Severity
CVSS 8.8 · High
Confidence
Confirmed
Exploit status
Trusted Third Party Report
EPSS
100.0%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-49704 is Microsoft SharePoint Remote Code Execution Vulnerability.

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Also reported by third-party sources. Confidence is confirmed.

Who is affected?

Microsoft SharePoint Enterprise Server 2016 and Microsoft SharePoint Server 2019, including affected before 16.0.5508.1000 and affected before 16.0.10417.20027.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Microsoft SharePoint Remote Code Execution Vulnerability

Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.

Microsoft Affected
Microsoft SharePoint Enterprise Server 2016
Before 16.0.5508.1000
Microsoft Affected
Microsoft SharePoint Server 2019
Before 16.0.10417.20027
View vendor advisory (opens in new tab)
Published
08 Jul 2025
Exploitation Attempts Reported
01 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

Tags

cisa microsoft malware metasploit_scanner

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

CVE

Recorded 01 Jun 2026

A trusted third party reported exploitation attempts.

Targeted by Malware-Related Exploitation Attempts

CVE

Recorded 02 Jun 2026

Exploitation attempts against this vulnerability are associated with malware-related payloads.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2026-06-01 10:37 UTC
CISA 2026-06-02 14:06 UTC
Unit 42 Timely Threat Intel 2026-10-27 21:51 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Metasploit https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/http/sharepoint_toolpane_rce.rb 08 Jul 2025

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.8 High

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

100.0%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Improper Control of Generation of Code ('Code Injection') CWE-94

Recent mention · Unit 42 Timely Threat Intel

2025-07-19 (SATURDAY): MICROSOFT SHAREPOINT VULNERABILITIES - CVE-2025-49704, CVE-2025-49706, CVE-2025-53770 AND CVE-2025-53771

2025-07-19 (SATURDAY): MICROSOFT SHAREPOINT VULNERABILITIES - CVE-2025-49704, CVE-2025-49706, CVE-2025-53770 AND CVE-2025-53771 REFERENCES: - https://www.linkedin.com/posts/unit42_active-exploitation-alert-microsoft-activity-7352419484726448128-oIOg/ -...

Read full advisory

All Mentions

Recent mention · Unit 42 Timely Threat Intel

2025-07-19 (SATURDAY): MICROSOFT SHAREPOINT VULNERABILITIES - CVE-2025-49704, CVE-2025-49706, CVE-2025-53770 AND CVE-2025-53771

Unit 42 Timely Threat Intel · 19 Jul 2025

2025-07-19 (SATURDAY): MICROSOFT SHAREPOINT VULNERABILITIES - CVE-2025-49704, CVE-2025-49706, CVE-2025-53770 AND CVE-2025-53771 REFERENCES: - https://www.linkedin.com/posts/unit42_active-exploitation-alert-microsoft-activity-7352419484726448128-oIOg/ - https://x.com/Unit42_Intel/status/1946654044316905883 - https://x.com/Unit42_Intel/status/1946763492985348248 ORIGINAL REFERENCES: - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49704 - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49706 - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53770...

Timeline

From disclosure to observed exploitation attempts

  1. 21:51 UTC

    KEV confirmed by Unit 42 Timely Threat Intel

    Exploitation attempts reported by an external source

  2. 14:06 UTC

    Targeted by malware-related exploitation attempts

    Malware-related exploitation attempts or payloads reported

  3. 14:06 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  4. 10:37 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  5. 16:58 UTC

    CVE published

    Vulnerability disclosed publicly

  6. 00:00 UTC

    Metasploit module available

    Exploit module available

  7. 19:59 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-49704

Sample API response 
{
  "cve_id": "CVE-2025-49704",
  "confidence": "Confirmed",
  "cvss_score": 8.8,
  "cvss_estimated": false,
  "epss_score": 0.99996,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}