Site Owner code execution via command injection
Published Sep 10, 2024 · Updated Aug 10, 2026
Command injection in Microsoft SharePoint Server allows remote authenticated users with Site Owner permissions to execute arbitrary code. Microsoft identifies the weakness as command injection but has not disclosed the affected component, input, or command-construction operation. Successful exploitation requires Site Owner permissions and runs injected code in the SharePoint Server context, allowing control of data and service behavior.
Summary
What happened
Command injection in Microsoft SharePoint Server allows remote authenticated users with Site Owner permissions to execute arbitrary code. Microsoft identifies the weakness as command injection but has not disclosed the affected component, input, or command-construction operation. Successful exploitation requires Site Owner permissions and runs injected code in the SharePoint Server context, allowing control of data and service behavior.
The record
- CVE
- CVE-2024-38227
- Published
- Sep 10, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft SharePoint Enterprise Server 2016
- Classifications
- CWE-77, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 10, 2024CVE 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=16.0.0 <16.0.5465.1001
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