dbcve.org
Sharepoint ServerApplication · Microsoft

CVE-2026-47298

HIGH · 8.0 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 16.0.19725.20384 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 authorization 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

Improper authorization vulnerability in Microsoft Office SharePoint enables authenticated users to bypass access controls and execute arbitrary code remotely. The flaw allows an authorized attacker to perform actions beyond their intended permission level, leading to code execution over the network.

MitigationApply Microsoft security updates for SharePoint when available; review and enforce least-privilege permissions for all user roles; audit custom SharePoint solutions for proper authorization checks.

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:< 16.0.19725.20384= 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
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 checks

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

  1. Check installed SharePoint Server version
    Open SharePoint Management Shell and run: (Get-SPFarm).BuildVersion.ToString() or check in Central Administration > System Settings > Manage farm configuration
    Affected if Version is 2016, 2019, or lower than 16.0.19725.20384
  2. Retrieve exact SharePoint build number
    Run: (Get-SPFarm).BuildVersion or check registry key HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\SharePoint\Setup\Version
    Affected if Build number is below 16.0.19725.20384 for any supported 2016/2019 or newer release
  3. Verify SharePoint web application configuration
    In Central Administration > Application Management > Manage web applications, list all web applications and their authentication methods
    Affected if Any web application is configured with classic or claims-based authentication that accepts user credentials
  4. Confirm presence of user accounts with site access
    Run: Get-SPUser -Web [URL] | Select-Object to enumerate users with any access level to site collections
    Affected if Any authenticated user accounts exist with permissions to SharePoint sites, regardless of permission level (since the flaw enables privilege escalation from any valid access)

A user is affected if their SharePoint Server installation is version 2016, 2019, or any build lower than 16.0.19725.20384, and the server accepts authenticated user access.

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
Upgrade available Upgrade to 16.0.19725.20384 or later
Fixed in 16.0.19725.20384
Interim mitigation

Apply Microsoft security updates for SharePoint when available; review and enforce least-privilege permissions for all user roles; audit custom SharePoint solutions for proper authorization checks.

Recommended fix Moderate confidence

Microsoft SharePoint Server version 16.0.19725.20384 or later

  1. Identify your current Microsoft SharePoint Server version by checking Central Administration > System Settings > Manage farm configuration
  2. Review the Microsoft Security Response Center (msrc.microsoft.com) for the specific KB article and patch associated with CVE-2026-47298
  3. Apply the appropriate security update for your SharePoint Server version (2016, 2019, or Subscription Edition)
  4. After patching, verify the fix by confirming the SharePoint version matches or exceeds 16.0.19725.20384
  5. Test critical SharePoint workflows to ensure normal functionality post-update
Caveat Standard SharePoint cumulative update apply procedures should be followed; test in non-production environment first

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

Fix this in Sharepoint Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47298 — 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-2026-47298 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