CVE-2026-47636
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 input during web page generation ('cross-site scripting') in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing 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 cross-site scripting (XSS) vulnerability in Microsoft Office SharePoint where improper neutralization of user input during web page generation allows attackers to inject malicious scripts into SharePoint pages. Successful exploitation could enable session hijacking, credential theft, or spoofing of legitimate content.
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.19725.20384= 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 SharePoint Server versionOpen SharePoint Management Shell and run: (Get-SPFarm).BuildVersion or check Central Administration > System Settings > Manage farm configurationAffected if The version number is less than 16.0.19725.20384, or equals 2016 or 2019 (any build)
-
Confirm SharePoint editionRun Get-SPProductInfo in SharePoint Management Shell to verify the specific SharePoint Server edition installed (2016, 2019, or Subscription/Server)Affected if Running SharePoint Server 2016 or 2019 editions, which are listed as affected regardless of build number
-
Identify custom or third-party web partsReview installed solutions using Get-SPSolution in SharePoint Management Shell, and check Central Administration > System Settings > Manage farm solutions for deployed .wsp filesAffected if Custom web parts or third-party solutions that accept and render user input are deployed; these could provide additional attack vectors for XSS injection
-
Audit pages with user input formsUse SharePoint Designer or site collection auditing to identify pages containing web parts that accept user input such as search boxes, discussion boards, or custom formsAffected if Pages exist that render user-supplied content without proper output encoding, which is the attack surface for this XSS flaw
-
Review Content Security Policy configurationCheck web.config files or IIS settings for CSP header configuration; in SharePoint Management Shell run: Get-WebConfigurationProperty -Filter /system.webServer/httpProtocol/customHeaders -Name collectionAffected if CSP headers are not configured or are set to overly permissive values, meaning the XSS payload could execute if injected
You are affected if running any version of SharePoint Server 2016 or 2019, or any SharePoint Subscription version prior to build 16.0.19725.20384, and your environment contains pages or web parts that render user input without encoding.
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 · scoped16.0.19725.20384
Apply Microsoft security updates for SharePoint when released; implement robust input validation and output encoding on SharePoint sites; configure Content Security Policy (CSP) headers to mitigate XSS execution.
SharePoint Server 2016 or 2019 with build >= 16.0.19725.20384 (latest available Cumulative Update)
- Identify your current SharePoint Server version (2016 or 2019) via SharePoint Administration Center or Get-SPFarm | Select BuildVersion
- Determine if your current build is below 16.0.19725.20384
- For SharePoint Server 2016: Install the latest Cumulative Update (CU) that meets or exceeds build version 16.0.19725.20384
- For SharePoint Server 2019: Install the latest Cumulative Update (CU) that meets or exceeds build version 16.0.19725.20384
- After applying the update, run the SharePoint Products Configuration Wizard (PSConfig) on all servers in the farm
- Verify the build version has been updated to 16.0.19725.20384 or later via Get-SPBuildVersion
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47636 — 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-2026-47636 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