FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2012-1854

Microsoft · Visual Basic for Applications (VBA) · Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability

Verdict
Patch soon · actively exploited, not reachable unauthenticated from the internet, and in the top 5% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-04-13 · exploited in the wild for 167 days

What an attacker can reach How likely Time What CISA says to do Sources All 545

What an attacker can reach

CVSS 7.8 HIGH. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectorlocalrequires local access to the machine
Privileges requirednoneneeds no credentials at all
User interactionrequiredneeds a user to click, load or submit something first
Base vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
WeaknessCWE-426

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.2103, which places it in the top 5% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.2103
Percentile0.975 — top 5%

Time

Added to KEV2026-04-13
Days exploited167
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.

Sources