CVE-2025-30397
Microsoft Windows Scripting Engine Type Confusion
- Published13 May 2025
- Added to CISA KEV13 May 2025
- Remediation due3 Jun 2025
Description
Access of resource using incompatible type ('type confusion') in Microsoft Scripting Engine allows an unauthorized attacker to execute code over a network.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-30397
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-30397
- https://www.vicarius.io/vsociety/posts/cve-2025-30397-type-confusion-vulnerability-in-microsoft-scripting-engine-detection-script
- https://www.vicarius.io/vsociety/posts/cve-2025-30397-type-confusion-vulnerability-in-microsoft-scripting-engine-mitigation-script
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-30397 being actively exploited?
Yes. CVE-2025-30397 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 13 May 2025.
How severe is CVE-2025-30397?
CVE-2025-30397 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 26.8% probability of exploitation.
Which products are affected by CVE-2025-30397?
Affected products include Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, and 10 more.
How do I fix CVE-2025-30397?
Upgrade affected software to a fixed version, for example Microsoft Windows 10 1507 10.0.10240.21014, Microsoft Windows 10 1607 10.0.14393.8066, Microsoft Windows 10 1809 10.0.17763.7314 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-30397 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.