CVE-2012-1854: Visual Basic for Applications Insecure Library Loading Vulnerability
- Vendor
- Microsoft Corporation
CVE-2012-1854 is an untrusted search path vulnerability in Microsoft Visual Basic for Applications (VBA). VBA incorrectly restricts the path used to load external libraries, allowing Microsoft Office to load an attacker-controlled DLL when a user opens a legitimate Office document located in the same directory. The DLL executes with the logged-on user's privileges. Affected products include Office 2003 SP3, Office 2007 SP2/SP3, Office 2010 with and without SP1, and VBA runtimes and SDK versions 6.3, 6.4, and 6.5, including vulnerable runtime copies distributed with third-party applications. Limited, targeted exploitation was acknowledged in July 2012.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution with the logged-on user's rights, enabling program installation, data viewing, modification or deletion, and account creation. Exploitation against a user with administrative privileges can result in complete system compromise; lower-privileged users limit the attacker's effective permissions. Office workstations and terminal servers are primarily exposed.
Mitigation
If you can’t patch tonight, do this now.
Use the workaround tool described in KB2264107 to restrict library loading from SMB and WebDAV shares. Disable the WebClient service and block TCP ports 139 and 445 where operationally feasible. These workarounds can disrupt WebDAV access and SMB-dependent services and do not replace updating vulnerable runtime copies. Operating Office with non-administrative privileges reduces the consequences of successful exploitation.
Remediation
Patch, then assume compromise.
Apply the applicable MS12-046 security updates. Office 2003 SP3 uses KB2687626, which replaced KB2598361 because of a certificate timestamp issue; systems that successfully installed KB2598361 do not require the replacement. Office 2007 SP2/SP3 uses KB2596744. Office 2010 and Office 2010 SP1 require both KB2598243 and KB2553447, installed in either order. Apply VBA runtime update KB2688865 where applicable and verify runtime version 6.5.10.54. Inventory third-party runtime copies using the guidance in KB978213: private copies outside the shared location may require application-vendor updates. Developers redistributing the runtime must obtain the updated VBA SDK from Summit Software Company and update their installers.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2012-1854 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 13, 2026.
- Is there a public exploit for CVE-2012-1854?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2012-1854.
- Is there a patch for CVE-2012-1854?
- Apply the applicable MS12-046 security updates. Office 2003 SP3 uses KB2687626, which replaced KB2598361 because of a certificate timestamp issue; systems that successfully installed KB2598361 do not require the replacement.
- What products are affected by CVE-2012-1854?
- Microsoft Corporation Microsoft Office, Microsoft Corporation Visual Basic For Applications, and Microsoft Corporation Visual Basic For Applications Sdk.
- How severe is CVE-2012-1854?
- CVE-2012-1854 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 20.9% (98th percentile) as of Oct 16, 2026.
Recent activity
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.