Skip to main content
ExploitedIn CISA KEV

CVE-2012-1854

Exploitation confirmed. First attested on 2012-07-10 by CISA-ADP, CISA KEV, GCVE · kevintel.

  • Published2012-07-10
  • WeaknessCWE-426

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2012-07-1021:00Listed as exploited by GCVEGCVE
  2. 2012-07-1021:00Exploitation first reportedGCVE
  3. 2012-07-1021:55CVE publishedNVD
  4. 2026-04-13Added to the CISA KEV catalogCISA KEV
  5. 2026-04-1317:00SSVC exploitation set to activeCISA-ADP
  6. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2012-1854?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2012-1854?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Microsoft office
BranchAffectedFixed in
2003.x= 2003no fix published
2007.x= 2007no fix published
2010.x= 2010no fix published
Microsoft visual basic for applications
BranchAffectedFixed in
—all versionsno fix published
Microsoft visual basic for applications sdk
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. CISA’s 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.due 2026-04-27

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

CISA Known Exploited Vulnerability

Date Added
2026-04-13
Patch Due Date
2026-04-27
Ransomware Use
Unknown
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.

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2012-07-10
Last Modified
2026-06-16
NVD status
Analyzed

Frequently asked questions

What is CVE-2012-1854?

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.

Is CVE-2012-1854 actively exploited?

Yes. CVE-2012-1854 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-04-27.

What is the CVSS score for CVE-2012-1854?

CVE-2012-1854 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.