Code execution via improper link resolution
Published Jun 11, 2024 · Updated Aug 10, 2026
Link-following in Microsoft Office 2016, 2019, LTSC 2021, and Microsoft 365 Apps allows attackers to execute code locally. Microsoft identifies improper link resolution before file access but has not published the affected component, file format, or code path that follows the attacker-controlled link. Exploitation requires local attack conditions and user interaction, and successful exploitation executes code with the affected user's privileges.
Summary
What happened
Link-following in Microsoft Office 2016, 2019, LTSC 2021, and Microsoft 365 Apps allows attackers to execute code locally. Microsoft identifies improper link resolution before file access but has not published the affected component, file format, or code path that follows the attacker-controlled link. Exploitation requires local attack conditions and user interaction, and successful exploitation executes code with the affected user's privileges.
The record
- CVE
- CVE-2024-30104
- Published
- Jun 11, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- CWE-59, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 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.5452.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