# Visual Basic for Applications vulnerabilities

> Visual Basic for Applications is made by Microsoft. We track 2 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 13 April 2026. Microsoft lists newer releases under their own names, such as Visual Basic for Applications SDK, so check those pages too.

Canonical page: https://www.precursorintelligence.com/product/microsoft/visual_basic_for_applications

## At a glance

- **Made by:** [Microsoft](https://www.precursorintelligence.com/vendors/microsoft)
- **Published vulnerabilities:** 2
- **Known to be exploited:** 1 (listed under the name Visual Basic for Applications)
- **Versions tracked:** 0
- **Most recently added to the known-exploited list:** [CVE-2012-1854](https://www.precursorintelligence.com/what-is/cve-2012-1854), 13 April 2026. We keep watching the list.

## Is Visual Basic for Applications listed under other names?

Microsoft also lists Visual Basic for Applications under more specific names, such as Visual Basic for Applications SDK. Flaws listed only under those names are counted on their own pages, not here.

- [Visual Basic for Applications SDK](https://www.precursorintelligence.com/product/microsoft/visual_basic_for_applications_sdk): 1 published vulnerability

## Which versions of Visual Basic for Applications do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published.

- [CVE-2012-1854](https://www.precursorintelligence.com/what-is/cve-2012-1854) (Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability): all versions

## Which Visual Basic for Applications vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited, newest first:

- [CVE-2012-1854](https://www.precursorintelligence.com/what-is/cve-2012-1854): Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability. Medium, CVSS 6.9, chance of use in 30 days 21%, known exploited since 13 April 2026.

## Questions

### How many vulnerabilities does Visual Basic for Applications have?

We track 2 published vulnerabilities listed under the name Visual Basic for Applications, across 0 versions. The most recent Visual Basic for Applications flaw added to the known-exploited list is CVE-2012-1854, on 13 April 2026.

### Which Visual Basic for Applications vulnerabilities are being exploited?

1 is on the list of flaws known to be exploited. The most recently added is CVE-2012-1854.

### Why are newer Visual Basic for Applications flaws missing from this page?

Microsoft also lists Visual Basic for Applications under more specific names, such as Visual Basic for Applications SDK. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

### Which versions of Visual Basic for Applications do the exploited flaws affect?

Each flaw names its own versions, usually as ranges. The newest, CVE-2012-1854, affects all versions. The versions for every exploited flaw are listed on this page.

### How do I get alerts for Visual Basic for Applications?

Create a Precursor Intelligence account and track Visual Basic for Applications. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.

## Running Visual Basic for Applications?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact

