dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Jul 2025. Known ransomware use
Sharepoint ServerApplication · Microsoft

CVE-2025-49704

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CVE-2025-49704 is a code injection vulnerability in Microsoft Office SharePoint where improper control of code generation allows an authenticated attacker to inject and execute arbitrary code remotely over the network. This stems from insufficient validation of user-supplied input being used in dynamic code construction contexts within SharePoint applications.

MitigationApply Microsoft security updates for SharePoint when released. Ensure SharePoint farms are fully patched and follow least-privilege principles for SharePoint user accounts to limit the attack surface for authorized attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sharepoint ServerApplication
Affected:= 2016= 2019

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SharePoint Server version
    Use SharePoint Administration Center, PowerShell (Get-SPFarm), or check installed updates in Windows Update history to determine the exact SharePoint Server version number
    Affected if The installed version matches 2016 or 2019 exactly (version equality indicated by = in the affected range)
  2. Confirm SharePoint code generation features are accessible
    Review SharePoint configuration settings related to code generation, custom workflows, or script execution features that could be leveraged for injection
    Affected if Code generation or script execution capabilities are enabled and accessible to authenticated users
  3. Verify authentication configuration
    Check SharePoint authentication methods and ensure proper authentication is required for accessing vulnerable code generation endpoints
    Affected if Anonymous or weak authentication is allowed on SharePoint sites providing access to code generation features
  4. Review user permissions to code generation functions
    Examine SharePoint user roles and permissions, particularly for users with contributor or developer-level access who could trigger code generation
    Affected if Authenticated users have elevated permissions that allow access to code generation or script execution interfaces

You are affected if your SharePoint Server is version 2016 or 2019 and authenticated users can access code generation or script execution features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for SharePoint when released. Ensure SharePoint farms are fully patched and follow least-privilege principles for SharePoint user accounts to limit the attack surface for authorized attackers.

Recommended fix Moderate confidence

Install the specific Security Update/Cumulative Update for SharePoint Server 2016 or 2019 as listed in the MSRC advisory for CVE-2025-49704

  1. Check the Microsoft Security Response Center (msrc.microsoft.com) for CVE-2025-49704 to identify the exact Knowledge Base (KB) article number for your SharePoint version
  2. For SharePoint Server 2016: Locate and install the specific Cumulative Update (CU) or Security Update referenced in the MSRC advisory
  3. For SharePoint Server 2019: Locate and install the specific Cumulative Update (CU) or Security Update referenced in the MSRC advisory
  4. Before applying the update, ensure you have a complete farm backup including database and configuration
  5. Test the update in a non-production environment first
  6. Apply the update during a planned maintenance window following Microsoft's standard SharePoint update process
  7. Verify the update installation was successful by checking the SharePoint version in Central Administration under 'Manage patch status' or 'Check product and inventory installation status'
  8. Monitor SharePoint services and web applications after the update to ensure normal operation
Caveat Standard SharePoint CU update risks apply - test thoroughly in non-production first; some farm configurations may require additional post-update steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sharepoint Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49704 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data