CVE-2022-24472
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 · uneditedMicrosoft SharePoint Server Spoofing Vulnerability
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 spoofing vulnerability in Microsoft SharePoint Server. The vulnerability allows an attacker to impersonate legitimate users or entities within the SharePoint environment, potentially gaining unauthorized access to sensitive data or performing actions with elevated privileges.
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= 2013all versions= 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Confirm SharePoint installationCheck if Microsoft SharePoint Server or SharePoint Foundation is installed on the server by reviewing installed programs in Control Panel > Programs and Features, or run 'Get-PnpDevice -Class Software | Where-Object {$_.FriendlyName -like "*SharePoint*"}' in PowerShellAffected if SharePoint Server or SharePoint Foundation is not found in the installed programs list, then the system is not affected by this vulnerability
-
Identify SharePoint versionRun 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\PID" | Select-Object Version, PID' for SharePoint 2016, or check the SharePoint Central Administration site under 'System Settings > Manage servers in this farm' to view the exact version numberAffected if The installed version is SharePoint Foundation 2013, SharePoint Server 2016, or SharePoint Server 2019, indicating the system falls within the affected version range
-
Check SharePoint build numberOpen SharePoint Central Administration, navigate to 'System Settings > Manage servers in this farm' and record the Build number (for example, 16.0.10310.5000 for SharePoint 2019 or 16.0.4999.5000 for SharePoint 2016)Affected if The build number is within the vulnerable build range for the detected version, as Microsoft security updates for this CVE modify the build number to a patched level
-
Verify patch installation statusCheck Windows Update history or review installed updates via 'Get-HotFix | Where-Object {$_.Description -like "*SharePoint*"}' in PowerShell to see if security updates addressing CVE-2022-24472 have been appliedAffected if No security update specifically addressing CVE-2022-24472 appears in the installed updates or hotfix list, meaning the vulnerability remains unpatched
-
Review SharePoint authentication settingsNavigate to SharePoint Central Administration > Application Management > Manage web applications > Authentication Providers to verify the enabled authentication methods (Windows, Forms, Claims, etc.)Affected if The SharePoint web applications are using authentication methods that rely on user impersonation features, which is the attack vector for this spoofing vulnerability
The environment is affected if SharePoint Server 2016 or 2019, or SharePoint Foundation 2013 is installed and the corresponding security update for CVE-2022-24472 has not been applied.
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 the relevant Microsoft security update for SharePoint Server. If a patch is unavailable, implement compensating controls such as strict access controls, multi-factor authentication, and monitoring for suspicious SharePoint activity.
March 2022 Cumulative Update or later for your respective SharePoint version (2013 Foundation, 2016, or 2019)
- Identify your current SharePoint build version via SharePoint Management Shell: (Get-SPFarm).BuildVersion
- For SharePoint Foundation 2013: Install the March 2022 security update (KB5002082) or later cumulative update
- For SharePoint Server 2016: Install the March 2022 security update (KB5002091) or later cumulative update
- For SharePoint Server 2019: Install the March 2022 security update (KB5002086) or later cumulative update
- Verify the patch was applied by re-running: (Get-SPFarm).BuildVersion and confirming the version matches or exceeds the March 2022 release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24472 — 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-2022-24472 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