Vulnerability record · CVE-2012-1854 · published 10 July 2012
CVE-2012-1854: Microsoft Office VBE6.dll Untrusted Search Path Privilege Escalation
Microsoft · Office
VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2/SP3, 2010 Gold/SP1, Microsoft VBA, and the Summit Microsoft VBA SDK loads a library from an untrusted search path. A local attacker who places a malicious DLL in the current working directory can get it loaded by the affected component. The flaw was exploited in the wild in July 2012.
Description
Untrusted search path vulnerability in VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1; Microsoft Visual Basic for Applications (VBA); and Summit Microsoft Visual Basic for Applications SDK allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a .docx file, aka "Visual Basic for Applications Insecure Library Loading Vulnerability," as exploited in the wild in July 2012.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Automated analysis
high priorityThe flaw is in CISA KEV with confirmed in-the-wild exploitation and a high EPSS score, though it requires local access and user interaction.
What it is
VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2/SP3, 2010 Gold/SP1, Microsoft VBA, and the Summit Microsoft VBA SDK loads a library from an untrusted search path. A local attacker who places a malicious DLL in the current working directory can get it loaded by the affected component. The flaw was exploited in the wild in July 2012.
Impact
An attacker gains code execution at the privilege level of the user who opens the crafted file, which can lead to full system compromise if that user has administrative rights.
Attack surface
Reached locally: the victim must open a file such as a .docx from a directory containing the attacker's Trojan horse DLL. No prior authentication is required, but user interaction (opening the file) is needed per the CVSS vector AV:L/UI:R.
Exploitation
CISA added this to the Known Exploited Vulnerabilities catalog with a due date of 2026-04-27, and the NVD description states it was exploited in the wild in July 2012. EPSS gives a 30-day probability of 0.21028 (97.4th percentile).
What to do
- Apply the Microsoft MS12-046 update for affected Office, VBA, and VBA SDK versions.
- If patching is not possible, discontinue use of the affected product per CISA BOD 22-01 guidance.
- Do not open Office documents from untrusted directories or locations where unknown DLLs may reside.
- Restrict write access to directories used to open Office documents to prevent DLL planting.
- Follow vendor mitigation guidance in MS12-046 for any interim workarounds.
Detection
- Monitor for unexpected DLL files created in directories alongside Office documents, especially VBE6.dll or similarly named libraries.
- Alert on Office processes loading DLLs from user-writable or document directories rather than System32.
- Review endpoint logs for Office applications spawning child processes after opening documents from untrusted paths.
- Hunt for known exploitation artifacts tied to the July 2012 in-the-wild activity referenced in the NVD description.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2012-1854 to the Known Exploited Vulnerabilities catalog on 13 April 2026 as "Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability". Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Federal deadline 27 April 2026.
Affected products
3 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.us-cert.gov/cas/techalerts/TA12-192A.html | US Government Resource |
| https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-046 | MitigationVendor Advisory |
| https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14950 | Broken Link |
| http://www.us-cert.gov/cas/techalerts/TA12-192A.html | US Government Resource |
| https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-046 | MitigationVendor Advisory |
| https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14950 | Broken Link |
| https://learn.microsoft.com/en-us/security-updates/SecurityBulletins/2012/ms12-046 | MitigationVendor Advisory |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2012-1854 | US Government Resource |
Track CVE-2012-1854 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2012-1854), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.