CVE-2025-53760
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 · uneditedServer-side request forgery (ssrf) in Microsoft Office SharePoint allows an authorized attacker to elevate privileges 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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Microsoft Office SharePoint. An authorized attacker can exploit this flaw to make the SharePoint server perform arbitrary network requests, potentially accessing internal resources and services that should not be externally reachable, thereby elevating privileges over the network.
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< 16.0.18526.20518= 2016= 2019CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed SharePoint Server versionOpen SharePoint Central Administration > System Settings > Manage server in this farm > Check the Version column in the server list. Or run: Get-SPFarm | Select-Object BuildVersionAffected if The version is less than 16.0.18526.20518, or the version indicates SharePoint Server 2016 or 2019
-
Confirm the specific SharePoint edition and buildRun Get-SPServerFarm or check the SharePoint version number against Microsoft's official version documentation to confirm if it matches 2016 or 2019 editionsAffected if The build corresponds to SharePoint Server 2016 or 2019 regardless of patch level shown
-
Review SharePoint Unified Logging System (ULS) logs for suspicious outbound requestsNavigate to the ULS log directory (typically C:\Program Files\Common Files\microsoft shared\Web Server Extensions\LOGS) and search for entries containing 'MakeRequest', 'WebRequest', or unexpected external URLs from the SharePoint service accountAffected if Logs show outbound HTTP/HTTPS requests to internal IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x) or unusual external domains initiated by SharePoint processes
-
Audit SharePoint external data connection configurationsOpen SharePoint Central Administration > Application Management > Manage service applications > Check any Business Connectivity Services or External Data connections for configurations that allow arbitrary URLsAffected if External data connections or BCS service applications are configured with dynamic URL parameters that could be manipulated to trigger unauthorized outbound requests
-
Monitor network traffic originating from the SharePoint serverUse network monitoring tools or Windows Firewall with Security Event Logging to review outbound connections from the SharePoint server, focusing on connections initiated by the SharePoint application pool accountAffected if The SharePoint server is making outbound connections to internal resources or services that are not part of normal SharePoint operations
You are affected if your SharePoint Server version is below 16.0.18526.20518, or if you are running SharePoint Server 2016 or 2019, and the server has made or is making suspicious outbound network requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data16.0.18526.20518
Apply Microsoft security patches for SharePoint when released. Until then, restrict network access to the SharePoint server and monitor outbound connections for suspicious patterns.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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