CVE-2025-47172
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 · uneditedImproper neutralization of special elements used in an sql command ('sql 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 confidenceSQL injection vulnerability in Microsoft Office SharePoint allows an authenticated attacker to inject malicious SQL commands through improper input handling, potentially leading to unauthorized code execution or data exfiltration.
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= 2016<= 16.0.18526.20396= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SharePoint Server versionRun PowerShell as administrator and execute: (Get-SPFarm).BuildVersionAffected if The version returned matches SharePoint 2016 (exact match) or is <= 16.0.18526.20396, or is SharePoint Server 2019 (exact match)
-
Check SharePoint build via registryInspect the registry key: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\SharePoint\Setup\VersionAffected if The value matches 16.0.x.x ranges corresponding to the affected versions above
-
Confirm SharePoint edition typeIn SharePoint Central Administration, go to Manage farm features or run: Get-SPFarm | Select-Object BuildVersion, VersionAffected if The server is running SharePoint Enterprise Server 2016 or SharePoint Server 2019 and the build falls within affected ranges
-
Verify authentication methods enabledIn Central Administration, navigate to Authentication Providers under Application Management to review enabled authentication modes (Windows, Forms, Trusted Identity providers)Affected if Any form of non-Windows or external authentication is enabled, allowing authenticated attackers to access the vulnerable query paths
You are affected if your SharePoint Server version is exactly 2016, is exactly 2019, or has a build number up to and including 16.0.18526.20396, and you have authentication configured that permits authenticated users to interact with SharePoint applications.
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.
dbcve · scopedApply Microsoft SharePoint security patches immediately; review and harden database query implementations; implement parameterized queries and input validation across SharePoint applications.
Install the May 2024 cumulative update for SharePoint Server 2016 or 2019 (specific CU version available on Microsoft Update Catalog)
- Check the Microsoft Security Response Center (msrc.microsoft.com) for the May 2024 security updates corresponding to this CVE
- Identify the specific cumulative update (CU) required for your SharePoint Server version (2016 or 2019)
- Download and install the corresponding cumulative update from the Microsoft Update Catalog
- After installation, run the SharePoint Products Configuration Wizard to apply the update
- Verify the installation by checking the SharePoint version matches the fixed build number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47172 — 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-47172 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