CVE-2025-30397

Scripting Engine Memory Corruption Vulnerability

HIGH

7.5

CVSS Score

Published: May 13, 2025 at 04:59 PM UTC

Updated: June 17, 2026 at 09:08 AM UTC

16 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploitation

CISA KEV

Exploit prediction

EPSS 27%

SSVC

Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score27.3%

EPSS (Exploit Prediction Scoring System) estimates a 27.3% chance this CVE is exploited in the wild within the next 30 days — higher than 98% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows Scripting Engine contains a type confusion vulnerability that allows an unauthorized attacker to execute code over a network via a specially crafted URL.

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.

Ransomware Use

Unknown

Added to KEV

May 13, 2025

Remediation Due

Jun 3, 2025

510 days overdue

Notes

https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-30397

https://nvd.nist.gov/vuln/detail/CVE-2025-30397

Description

Access of resource using incompatible type ('type confusion') in Microsoft Scripting Engine allows an unauthorized attacker to execute code over a network.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Windows 10 1507 · Microsoft

95%

v < 10.0.10240.2101410.0.10240.0 ≤ v < 10.0.10240.2101410.0.10240.0

Affected range stops below 10.0.10240.21014, so it looks safe — our inference, not a vendor statement

Windows 10 1607 · Microsoft

95%

v < 10.0.14393.806610.0.14393.0 ≤ v < 10.0.14393.806610.0.14393.0

Affected range stops below 10.0.14393.8066, so it looks safe — our inference, not a vendor statement

Windows 10 1809 · Microsoft

95%

v < 10.0.17763.731410.0.17763.0 ≤ v < 10.0.17763.731410.0.17763.0

Affected range stops below 10.0.17763.7314, so it looks safe — our inference, not a vendor statement

Windows 10 21H2 · Microsoft

95%

v < 10.0.19044.585410.0.19044.0 ≤ v < 10.0.19044.585410.0.19044.0

Affected range stops below 10.0.19044.5854, so it looks safe — our inference, not a vendor statement

Windows 10 22H2 · Microsoft

95%

v < 10.0.19045.585410.0.19045.0 ≤ v < 10.0.19045.585410.0.19045.0

Affected range stops below 10.0.19045.5854, so it looks safe — our inference, not a vendor statement

Windows 11 22H2 · Microsoft

95%

v < 10.0.22621.533510.0.22621.0 ≤ v < 10.0.22621.533510.0.22621.0

Affected range stops below 10.0.22621.5335, so it looks safe — our inference, not a vendor statement

Windows 11 23H2 · Microsoft

95%

v < 10.0.22631.533510.0.22631.0 ≤ v < 10.0.22631.533510.0.22631.0

Affected range stops below 10.0.22631.5335, so it looks safe — our inference, not a vendor statement

Windows 11 24H2 · Microsoft

95%

v < 10.0.26100.398110.0.26100.0 ≤ v < 10.0.26100.406110.0.26100.0

Affected range stops below 10.0.26100.4061, so it looks safe — our inference, not a vendor statement

Windows Server 2008 · Microsoft

95%

6.0.6003.0 ≤ v < 6.0.6003.232796.1.7601.0 ≤ v < 6.1.7601.277296.0.6003.0 6.1.7601.0 r2 sp1sp2

Affected range stops below 6.0.6003.23279, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.7601.27729, so it looks safe — our inference, not a vendor statement

Windows Server 2012 · Microsoft

95%

6.2.9200.0 ≤ v < 6.2.9200.254756.3.9600.0 ≤ v < 6.3.9600.225776.2.9200.0 6.3.9600.0 r2

Affected range stops below 6.2.9200.25475, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.3.9600.22577, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor AdvisoryPatch

Source: [email protected]

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-30397

ExploitThird Party Advisory

Source: af854a3a-2127-422b-91ae-364da2661108

https://www.vicarius.io/vsociety/posts/cve-2025-30397-type-confusion-vulnerability-in-microsoft-scripting-engine-detection-script

MitigationThird Party Advisory

Source: af854a3a-2127-422b-91ae-364da2661108

https://www.vicarius.io/vsociety/posts/cve-2025-30397-type-confusion-vulnerability-in-microsoft-scripting-engine-mitigation-script

US Government Resource

Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-30397

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHmicrosoft

Vector?

Quick Info

StatusANALYZED

CWE

CWE-843

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card