CVE Alert: CVE-2025-49704 – Microsoft – Microsoft SharePoint Enterprise Server 2016

CVE-2025-49704

HIGHCISA KEVExploitation active

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

CVSS v3.1 (8.8)
Vendor
Microsoft, Microsoft
Product
Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019
Versions
16.0.0 lt 16.0.5508.1000 | 16.0.0 lt 16.0.10417.20027
CWE
CWE-94, CWE-94: Improper Control of Generation of Code (‘Code Injection’)
Vector
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
Published
2025-07-08T16:58:05.908Z
Updated
2025-08-18T17:51:30.909Z

AI Summary Analysis

**Risk verdict**: Critical risk with active exploitation; treat as Priority 1 and remediate immediately.

**Why this matters**: An attacker can remotely execute arbitrary code on vulnerable on‑premises servers with no user interaction, potentially taking full control and persisting inside the environment. The impact includes data compromise, service disruption, and lateral movement into adjacent assets via trusted pathways.

**Most likely attack path**: Exploitation requires network access to the web front‑end, with only low privileges needed. Initial access could occur through internet‑facing endpoints or VPN access; once compromised, the attacker can execute code on the server, establish persistence, and move laterally to other systems through trust relationships or shared services.

**Who is most exposed**: Organisations running on‑premises deployments that expose web endpoints to the internet or to broad corporate networks are highest risk, particularly where network segmentation and access controls are weak.

Detection ideas

  • Anomalous process creation on web front‑end/application pool processes.
  • Unusual code‑injection patterns or unexpected child processes in web app services.
  • Sudden spikes in outbound traffic or data transfers from the server.
  • New services, scheduled tasks, or web‑config/file changes indicative of persistence.
  • Unauthorised access attempts to admin or management endpoints.

Mitigation and prioritisation

  • Patch the affected versions immediately; treat as Priority 1; validate in a test env before wide rollout.
  • If patching cannot be applied quickly, harden exposure: restrict inbound access to approved IPs, enable WAF rules, and tighten network segmentation.
  • Enforce strong admin authentication, enable EDR on the server, and monitor for persistence or lateral‑movement indicators.
  • Confirm backups and run disaster‑recovery tests; coordinate with SOC and change‑management for a rapid remediation window.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.