Security readout for executives and security teams
Plain-English summary
An authenticated attacker could manipulate a file name or path in affected Microsoft SharePoint Server products to misrepresent content and potentially expose sensitive information. The issue is network-accessible and requires no user interaction, but the attacker must already have authorized access.
Executive priority
Treat as a moderate-priority confidentiality issue. Schedule prompt remediation, accelerating systems containing sensitive information or serving large authenticated populations. There is no supplied evidence of active exploitation, but network reachability, low complexity, and no required user interaction reduce defensive margin.
Technical view
CVE-2026-54108 is a CWE-73 external file-name or path control weakness affecting listed SharePoint Server products. CVSS 3.1 is 6.5: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality impact but no stated integrity or availability impact.
Likely exposure
Potential exposure exists in SharePoint Enterprise Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition deployments identified by the source bundle. Risk is greater where many users have authenticated access or sensitive documents are stored. Exact vulnerable build ranges should be confirmed through Microsoft's advisory.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires an authorized attacker with network access and low privileges. No exploit procedure or specific indicators of compromise are provided.
Researcher notes
The CVSS vector reports AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, with exploit maturity unproven and an official remedy available. Public detail in the bundle is limited to external file-name or path control and spoofing; affected build boundaries, attack mechanics, and detection indicators require confirmation from Microsoft.
Mitigation direction
Review Microsoft's advisory and apply the security update applicable to each affected SharePoint deployment.
Prioritize externally reachable or broadly accessible SharePoint systems and restrict unnecessary authenticated access until updating.
Use normal change control and back up configurations before remediation.
Validation and detection
Inventory SharePoint Enterprise Server 2016, Server 2019, and Subscription Edition deployments.
Compare each server's build and installed updates with Microsoft's CVE advisory.
Test remediation outside production, then verify SharePoint service health and access controls after rollout.
Review relevant SharePoint and authentication logs; the supplied sources provide no specific indicators.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.