Threats / Microsoft / CVE-2025-49704
CVE-2025-49704
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft SharePoint vulnerability
Microsoft SharePoint code injection vulnerability (CWE-94) allows authorized attackers to execute arbitrary code over a network. Actively exploited in ransomware campaigns with a known patch bypass.
Verdict
Today item, not a backlog item.
High-risk code injection in SharePoint enabling remote code execution by authenticated users. Active exploitation in ransomware operations and existence of patch bypass (CVE-2025-53770) elevate threat severity despite lack of CVSS score.
CISA KEV Yes · 2025-07-225Ransomware use Flagged5EPSS 0.99915 (verify live)6CVSS 8.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4Exploit Weaponized · public exploit · Metasploit module15
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
68 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-22), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99915 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C) · Affected: Microsoft, SharePoint. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 14 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial access as an authorized SharePoint user through compromised credentials or insider access.
Business
Attacker establishes foothold within trusted collaboration infrastructure with legitimate user privileges.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject malicious code through SharePoint functionality that fails to sanitize user input, triggering code execution.
Business
Arbitrary code runs within SharePoint processes, bypassing perimeter defenses that trust internal applications.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate privileges and move laterally across the network to deploy ransomware or exfiltrate sensitive data.
Business
Ransomware encrypts critical business systems; data theft exposes confidential information and regulatory exposure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05