CVE-2025-30397
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAccess of resource using incompatible type ('type confusion') in Microsoft Scripting Engine allows an unauthorized attacker to execute code over a network.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceType confusion vulnerability in Microsoft Scripting Engine where the engine improperly handles objects of incompatible types, allowing an attacker to manipulate memory and achieve remote code execution. The vulnerability is exploitable over a network without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.10240.21014< 10.0.14393.8066< 10.0.17763.7314< 10.0.19044.5854< 10.0.19045.5854< 10.0.22621.5335< 10.0.22631.5335< 10.0.26100.3981CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version and build numberRun 'winver' or execute 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell to retrieve the exact Windows buildAffected if The build number falls below these thresholds: Windows 10 1507 < 10.0.10240.21014, 1607 < 10.0.14393.8066, 1809 < 10.0.17763.7314, 21h2 < 10.0.19044.5854, 22h2 < 10.0.19045.5854; Windows 11 22h2 < 10.0.22621.5335, 23h2 < 10.0.22631.5335, 24h2 < 10.0.26100.3981
-
Verify Scripting Engine components are presentCheck for existence of JScript.dll and VBScript.dll in System32 folder using 'Get-ChildItem C:\Windows\System32\jscript.dll, C:\Windows\System32\vbscript.dll'Affected if Either JScript.dll or VBScript.dll is present on the system (vulnerability requires these scripting engine components to be present)
-
Confirm scripting is accessible to applicationsCheck if scripting engine is enabled for web content by examining Internet Explorer or Edge legacy mode settings, or by verifying whether script files (.js, .vbs) can be executedAffected if Users can process JavaScript or VBScript through browsers, email clients, or document applications (vulnerability is triggerable when scripting engine processes untrusted script content)
A system is affected if it runs an unpatched Windows version within the affected build ranges AND has JScript or VBScript scripting engine components available to process untrusted script content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.10240.2101410.0.14393.806610.0.17763.7314
Apply Microsoft security updates for the Scripting Engine when released; until then, restrict network exposure, disable unnecessary scripting components, and employ defense-in-depth controls such as EDR and application whitelisting.
Windows 10 1507: build 10.0.10240.21014 | Windows 10 1607: build 10.0.14393.8066 | Windows 10 1809: build 10.0.17763.7314 | Windows 10 21h2: build 10.0.19044.5854 | Windows 10 22h2: build 10.0.19045.5854 | Windows 11 22h2: build 10.0.22621.5335 | Windows 11 23h2: build 10.0.22631.5335 | Windows 11 2
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest cumulative update for your Windows version
- Alternatively, manually download the specific Cumulative Update for your Windows version from the Microsoft Update Catalog
- Restart the system after the update is installed
- Verify the installed build number matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30397 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data