Skip to main content
VulnerabilityPublished Updated

CVE-2025-53760: Microsoft SharePoint Enterprise Server 2016 · Server-Side Request Forgery (SSRF)

Affects Microsoft SharePoint Enterprise Server 2016Source CVE Database V5

0

Not known to be exploited · 18% EPSS · CVSS 7.1 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
18.9% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft SharePoint Enterprise Server 2016Affected
  • =16.0.0
Fixed in–

AI-suggested

1. Monitor Microsoft’s official channels closely for the release of security patches addressing CVE-2025-53760 and apply them immediately upon availability. 2. Until patches are available, restrict SharePoint server outbound network access using firewall rules or network segmentation to limit the ability of SSRF to reach internal resources. 3. Implement strict access controls and least privilege principles for SharePoint users and service accounts to minimize the risk posed by authorized attackers. 4. Enable detailed logging and monitoring of SharePoint server network activity, focusing on unusual or unexpected outbound HTTP requests that could indicate SSRF exploitation attempts. 5. Conduct internal vulnerability assessments and penetration testing to identify potential SSRF attack vectors within the SharePoint environment. 6. Review and harden SharePoint configurations to disable or restrict features that allow external or internal URL fetching if not required. 7. Educate IT and security teams about SSRF risks and detection techniques specific to SharePoint environments. 8. Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to provide an additional layer of defense.

Description

Server-side request forgery (ssrf) in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network.

References

Community reviews

Loading reviews…