Service-account code execution via CAB path traversal
Published Jul 14, 2021 · Updated Aug 10, 2026
Path traversal in Microsoft SharePoint Server allows attackers to execute service-account code via a crafted CAB file. CabUtility's ExtractCab routine fails to validate user-supplied filenames before using their paths in file operations, permitting extraction outside the intended directory. Exploitation requires user interaction, adjacent-network access, and another vulnerability in a chain; successful execution runs in the SharePoint service-account context.
Summary
What happened
Path traversal in Microsoft SharePoint Server allows attackers to execute service-account code via a crafted CAB file. CabUtility's ExtractCab routine fails to validate user-supplied filenames before using their paths in file operations, permitting extraction outside the intended directory. Exploitation requires user interaction, adjacent-network access, and another vulnerability in a chain; successful execution runs in the SharePoint service-account context.
The record
- CVE
- CVE-2021-34468
- Published
- Jul 14, 2021
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft SharePoint Foundation 2013
- Classifications
- T1204.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.0.0 <15.0.5363.1000
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo