Microsoft rates the vulnerability Important, with a CVSS base score of 9.0. The remediation is specific: KB5002945, mapped to fixed build 16.0.20326.20278.
How the SharePoint attack works
According to Microsoft’s advisory, improper neutralization of input during web page generation—cross-site scripting, classified as CWE-79—allows an authorized attacker to perform spoofing over a network.
The attack depends on two distinct conditions:
- An authenticated attacker has permission to add or modify content on an affected SharePoint page and stores malicious script content there.
- Another user views and interacts with that content, allowing the script to run in that user’s security context.
The potential consequence goes beyond a misleading page: Microsoft says the attacker could access or modify SharePoint data available to the user encountering the malicious content. The relevant security boundary is therefore between the attacker’s content-editing permissions and the victim’s access to data.
Microsoft also explicitly states that the Preview Pane is not an attack vector. That distinction matters operationally: avoiding the Preview Pane does not address the described route through affected SharePoint page content.
Severity, scores and exploitation status
Microsoft’s advisory supplies the following assessment:
| Field | Advisory value |
|---|---|
| CVE | CVE-2026-109454 |
| Exact title | Microsoft Office SharePoint Spoofing Vulnerability |
| Severity | Important |
| CVSS base score | 9.0 |
| CVSS temporal score | 7.8 |
| Weakness | CWE-79 |
| Exploitation assessment | Exploitation Less Likely |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
The vector describes a network-accessible attack with low attack complexity, low privileges required and user interaction required. It also records changed scope and high potential impacts on confidentiality, integrity and availability.
Those details help reconcile the high numerical score with the attack prerequisites. This is not described as an unauthenticated attack that succeeds merely because a server is reachable: the attacker needs content permissions, and another user must interact with affected content. Nevertheless, those prerequisites do not make the potential data exposure trivial.
“Exploitation Less Likely” is Microsoft’s assessment, not a reason to disregard the update. Likewise, the Important severity label and the 9.0 base score are separate advisory fields; neither should be silently substituted for the other.
Affected product and exact fix
| Affected product | Security update | Vendor fixed version |
|---|---|---|
| Microsoft SharePoint Server Subscription Edition (x64) | KB5002945 | 16.0.20326.20278 |
Microsoft’s remediation is:
For Microsoft SharePoint Server Subscription Edition (x64), install KB5002945 to reach fixed build 16.0.20326.20278.
For administrators, this mapping provides a concrete verification target. A deployment record naming the update and a resulting build check answer different questions: whether the intended package was deployed, and whether the affected installation reached the specified fixed version.
What administrators should prioritize
The practical response follows directly from the advisory’s attack conditions and remediation:
- Identify affected installations. Scope the deployment work to Microsoft SharePoint Server Subscription Edition (x64).
- Deploy the specified fix. Use KB5002945 and verify the resulting build against 16.0.20326.20278 through established update-management procedures.
- Review content-editing permissions. Because the described attacker must be able to add or modify page content, unnecessary editing rights deserve attention. This is risk-reduction guidance derived from the attack prerequisites, not a replacement for patching.
- Keep validation focused on the actual attack surface. The advisory describes stored script in SharePoint page content, not a Preview Pane exploit.
The central lesson is straightforward: trusted collaboration content can become a vehicle for crossing user security boundaries. Correcting the vulnerable input handling is the prescribed fix; tighter publishing permissions complement that work but do not supersede it.
References
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com