{"id":"CVE-2019-0666","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-0666","generatedAt":"2026-10-28T20:13:01.651Z","title":"A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka 'Windows VBScript Engine Remote Code Execution Vulnerability'.","description":"A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka 'Windows VBScript Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0665, CVE-2019-0667, CVE-2019-0772.","published":"2019-04-08T23:29:01.000Z","lastModified":"2026-06-17T02:08:40.000Z","status":"Modified","sourceIdentifier":"secure@microsoft.com","cvss":{"version":"3.0","score":7.5,"severity":"HIGH","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H"},"cwe":["CWE-787"],"affected":["microsoft/internet explorer"],"epss":{"score":0.20403,"percentile":0.97478,"date":"2026-10-27","history":[{"date":"2026-09-21","score":0.22535,"percentile":0.97653},{"date":"2026-09-22","score":0.20403,"percentile":0.97371}]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"urgent","text":"EPSS puts the probability of exploitation in the next 30 days at 20.4%, higher than 97% of all known CVEs. Patch or mitigate before the next change window."},"changes":[],"references":[{"url":"https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0666","tags":["Patch","Vendor Advisory"],"source":"secure@microsoft.com"},{"url":"https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0666","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-0666","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}