NewsCompaniesFlawsGuides
Get the app

CVE-2012-1854

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Microsoft Visual Basic for Applications (VBA). For every flaw being used in attacks, see Exploited flaws; for Microsoft’s, see Microsoft flaws being used in attacks.

CVE-2012-1854 is a security flaw in Microsoft Visual Basic for Applications (VBA). Someone who already has a way in can use Microsoft Visual Basic for Applications (VBA) to run their own code. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 13 Apr 2026.[1]

Microsoft Visual Basic for Applications (VBA) is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Microsoft has published a fix or advice.

Description

CISA calls it a visual basic for applications insecure library loading in Microsoft Visual Basic for Applications (VBA). In its words: “Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is CWE-426, in MITRE’s list of common software weaknesses.

It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Microsoft’s advisory has them[3]. CISA names the product as Microsoft Visual Basic for Applications (VBA).

Most families won’t have Microsoft Visual Basic for Applications (VBA); it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 13 Apr 2026, 5,025 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 27 Apr 2026 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 21%. That’s in the top 3% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Microsoft has published a fix or advice.[3] 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.”[1]

  1. Check whether you use it.Microsoft Visual Basic for Applications (VBA) is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 27 Apr 2026 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 21%.[4]

See also

Other Microsoft flaws

  • CVE-2026-96951, Microsoft Windows: command injection ·
  • CVE-2026-65660, Microsoft SharePoint: code injection ·
  • CVE-2026-85880, Microsoft Windows: heap-based buffer overflow ·
  • CVE-2026-81963, Microsoft Windows: link following ·
  • CVE-2019-1068, Microsoft SQL Server: remote code execution ·

Added the same day

  • CVE-2026-34621, Adobe Acrobat and Reader: prototype pollution ·
  • CVE-2026-21643, Fortinet FortiClient EMS: SQL injection ·
  • CVE-2025-60710, Microsoft Windows: link following ·
  • CVE-2023-36424, Microsoft Windows: out-of-bounds read ·
  • CVE-2023-21529, Microsoft Exchange Server: deserialization of untrusted data ·

Every Microsoft flaw on CISA’s list · Everything added in April 2026

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability”. Known Exploited Vulnerabilities Catalog, added 13 Apr 2026.
  2. ^ National Institute of Standards and Technology. “CVE-2012-1854 Detail”. National Vulnerability Database, published 10 Jul 2012.
  3. ^ Microsoft. Advisories and fixes: learn.microsoft.com, docs.microsoft.com, learn.microsoft.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.209, percentile 97.5, 31 Oct 2026.
  5. CVE Program. “CVE-2012-1854”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.