CVERadar
HIGH · CVSS 3.1 7.8CISA KEV · added 2026-04-13EPSS 20.87% (p98)Threat level 60

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

Microsoft · Visual Basic for Applications (VBA) · NVD published 2012-07-11 · posted 2026-04-13 · last modified 2026-06-17

What it is

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.

WeaknessCWE-426
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
CISA due date2026-04-27 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsExecution → Stealth

Exploitation evidence

First exploit evidence seen: 2026-04-13 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2026-04-13. Source

Sources: CISA KEV.

Defend the Chain

The attack chain for CVE-2012-1854 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 60/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1574.008 Path Interception by Search Order Hijacking Inferred

Inferred from CWE CWE-426

How to fix it

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. (source: CISA KEV)

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1038 Execution Prevention (for T1574.008) : Adversaries will likely need to place new binaries in locations to be executed through this weakness. Identify and block potentially malicious software executed path interception by using application control tools, like Windows Defender Application Control, AppLocker, or Software Restriction Policies where appropriate.
  • M1022 Restrict File and Directory Permissions (for T1574.008) : Ensure that proper permissions and directory access control are set to deny users the ability to write files to the top-level directory <code>C:</code> and system directories, such as <code>C:\Windows\</code>, to reduce places where malicious files could be placed for execution. Require that all executables be placed i
  • M1047 Audit (for T1574.008) : Find and eliminate path interception weaknesses in program configuration files, scripts, the PATH environment variable, services, and in shortcuts by surrounding PATH variables with quotation marks when functions allow for them. Be aware of the search order Windows uses for executing or loading binaries and use fully q

Detection Generic guidance

  • Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources