Outdated Microsoft Office
Hosts run Microsoft Office builds that are missing security updates, or an Office release that is out of support.
| Severity | High |
| CVSS 3.1 | 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 8.5 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1395: Dependency on Vulnerable Third-Party Component |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1203 Exploitation for Client Execution, T1566.001 Spearphishing Attachment |
| Category | Outdated Components |
Description
Microsoft Office installations on one or more hosts are missing security updates, or are an Office release that has passed the end of its support. Microsoft releases Office security fixes monthly. Microsoft 365 Apps and recent volume-licensed Office releases are installed with Click-to-Run and update themselves from an update channel, such as Current Channel, Monthly Enterprise Channel or Semi-Annual Enterprise Channel, unless updates are disabled, deferred or pointed at an internal source that is not kept current. Older MSI-based releases receive updates through Microsoft Update or WSUS.
Office vulnerabilities are mainly memory corruption and logic flaws triggered when a user opens, or in some cases previews, a crafted document, workbook, presentation or email. An attacker can send such a file by email or host it on a website and, if a user on an affected host opens it, run code with that user's privileges, gaining a foothold on the network. Office flaws are a long-standing phishing vector: the Equation Editor flaw CVE-2017-11882 was still used in malware campaigns years after its fix, and many Office vulnerabilities are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue. The impact rises where users have local administrator rights, and falls where macros and external content are restricted, Protected View is enforced, and attack surface reduction rules stop Office applications from creating child processes.
The finding is identified by an authenticated scan that compares the installed Office build with the builds listed in Microsoft's security update notes, and scanners report one result per missing monthly update. Hosts on the Semi-Annual Enterprise Channel legitimately run older feature versions and should be compared with that channel's latest security build rather than with Current Channel. Office installations on terminal servers and virtual desktop hosts, and separately installed products such as Visio and Project, are commonly missed.
Remediation
Keep every Office installation on a current, supported build:
- For Click-to-Run installations, ensure automatic updates are enabled and come from a source that is kept current, such as Microsoft's content delivery network, Configuration Manager or Intune, and choose an update channel the organisation can keep up with; Monthly Enterprise Channel delivers one predictable update each month.
- For MSI-based installations, enable Microsoft Update for other Microsoft products and approve Office security updates in WSUS or the patch management tool.
- Migrate installations of Office releases that have reached end of support to a supported release.
- Find hosts where updates have stalled, for example because Office has been left open for long periods or a Group Policy setting disables updates, and correct the cause.
- Reduce the impact of future flaws by blocking macros in files from the internet, enforcing Protected View, and enabling attack surface reduction rules where Microsoft Defender is used.
Confirm the fix by checking the build under File, Account in an Office application or in the management tool's update compliance reports, and repeating the scan.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.