How severe is CVE-2012-1854?

CVE-2012-1854 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2012-1854?

Affected package information for CVE-2012-1854 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2012-1854?

No fixed version has been published for CVE-2012-1854 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2012-1854 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2012-1854, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2012-1854 has an EPSS (Exploit Prediction Scoring System) score of 3.8%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2012-1854 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2012-1854 (Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-04-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-04-27. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2012-1854?

CVE-2012-1854 is classified as CWE-426 (CWE-426). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2012-1854?

CVE-2012-1854 affects microsoft office (3 versions, e.g. 2003, 2007, 2010); microsoft visual basic for applications; microsoft visual basic for applications sdk. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2012-1854 published, and has it been updated?

CVE-2012-1854 was published on July 10, 2012 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-04-13 — agencies required to remediate by 2026-04-27

CVE-2012-1854

HIGH

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…

Published

Jul 10, 2012

Updated

Apr 22, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

3.8%probability of exploitation in next 30 days

Lower Risk88th percentile-0.23%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

3 products · 9 configurations

Application

officemicrosoft

3 versions

200320072010

Application

visual basic for applicationsmicrosoft

all

Application

visual basic for applications sdkmicrosoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Untrusted search path vulnerability in VBE6.dll in Microsoft Office 2003…

nvd.nist.govNVDOct 2018

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-1854 in your stack?

O3 detects CVE-2012-1854 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works