Skip to content
Server Security Center
KEVhigh7.8

CVE-2012-1854: Microsoft Visual Basic for Applications Insecure Library Loading

Microsoft Visual Basic for Applications (VBA) · listed in the CISA catalog of actively exploited vulnerabilities since 2026-04-13.

CVSS v3.1 (CISA ADP)
7.8
high
EPSS (exploit probability, 30 days)
21%
higher than 97.6% of all CVEs
Added to CISA KEV
2026-04-13
US federal due date 2026-04-27
Automatable (CISA SSVC)
no
technical impact: total

CVE-2012-1854 explained

CVE-2012-1854 is an untrusted search path flaw in VBE6.dll used by Microsoft Visual Basic for Applications (VBA), Microsoft Office 2003 SP3, 2007 SP2 and SP3, 2010 Gold and SP1, and the Summit Microsoft Visual Basic for Applications SDK. A malicious DLL placed in the current working directory can be loaded, letting local users gain privileges. CISA lists it as known exploited.

Impact

An attacker who places a Trojan horse DLL in a directory, for example one containing a .docx file, can have it loaded when a user works from that directory. This leads to privilege gain with high impact on confidentiality, integrity and availability. User interaction is required and the attack vector is local. CISA rates technical impact as total and exploitation as not automatable. The description says it was exploited in the wild in July 2012.

Who is affected

The description names VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1, Microsoft Visual Basic for Applications (VBA), and the Summit Microsoft Visual Basic for Applications SDK. The CVE record itself lists no affected versions for Microsoft Visual Basic for Applications (VBA). The record names no fixed version.

Written with AI from the data on this page and checked against it automatically.

Official 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.

CISA 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.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2026-04-27 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's updates or mitigations for CVE-2012-1854 as described in the vendor advisory.
  2. Identify systems running the listed Office versions or VBA components and confirm their patch status.
  3. If mitigations cannot be applied, discontinue use of the affected product, as CISA's required action states.
  4. Warn users not to open documents from untrusted folders, shares or removable media.
  5. Check systems for unexpected DLL files placed next to documents, as a sign of compromise.

The CVE record names no fixed version. Follow the Microsoft vendor advisory for updates and mitigations. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Meanwhile, limit opening documents from untrusted locations.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-426 Untrusted Search Path

Questions about CVE-2012-1854

Is CVE-2012-1854 being exploited?
Yes. The description states it was exploited in the wild in July 2012, and CISA added it to its Known Exploited Vulnerabilities catalog on 2026-04-13 with a US federal due date of 2026-04-27. Ransomware use is listed as unknown.
Can it be exploited remotely without user action?
No. The attack vector is local and user interaction is required. A user must work in a directory that contains the attacker's malicious DLL, such as one holding a .docx file. CISA rates it as not automatable.
Which Office versions are mentioned?
The description names Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1, plus Microsoft Visual Basic for Applications (VBA) and the Summit Microsoft Visual Basic for Applications SDK.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.