CVE-2025-68623
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 · uneditedIn Microsoft DirectX End-User Runtime Web Installer 9.29.1974.0, a low-privilege user can replace an executable file during the installation process, which may result in unintended elevation of privileges. During installation, the installer runs with HIGH integrity and downloads executables and DLLs to the %TEMP% folder - writable by standard users. Subsequently, the installer executes the downloaded executable with HIGH integrity to complete the application installation. However, an attacker can replace the downloaded executable with a malicious, user-controlled executable. When the installer executes this replaced file, it runs the attacker's code with HIGH integrity. Since code running at HIGH integrity can escalate to SYSTEM level by registering and executing a service, this creates a complete privilege escalation chain from standard user to SYSTEM. NOTE: The Supplier disputes this record stating that they have determined this to be the behavior as designed.
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 · high confidenceA race condition and improper file handling vulnerability in Microsoft DirectX End-User Runtime Web Installer allows standard users to replace executables in the %TEMP% folder (writable by any user) after download but before execution. The installer then executes the malicious file with HIGH integrity, which can escalate to SYSTEM privileges via service registration, achieving complete privilege escalation from standard user to SYSTEM.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Identify installed DirectX installer versionCheck registry key HKLM\SOFTWARE\Microsoft\DirectX\InstalledVersion or look in Add/Remove Programs for 'Microsoft DirectX End-User Runtime Web Installer' and note the versionAffected if Version matches 9.29.1974.0 exactly
-
Verify TEMP folder is writable by standard usersOpen Command Prompt as a standard user and run 'echo test > %TEMP%\test.txt' to confirm write access; by default %TEMP% allows write for all usersAffected if Command succeeds, confirming standard users can place files in TEMP
-
Look for DirectX installer temporary filesSearch %TEMP% for recently created .exe or .dll files matching DirectX installer patterns (dxsetup.exe, dxwebsetup.exe, or similar) using 'dir %TEMP%\*.exe /o-d'Affected if Recent executable files from the DirectX installer are found in TEMP
-
Audit for unauthorized service creationRun 'sc query' to list all services, then compare against known-good baseline or look for unfamiliar services with SYSTEM privilege that appeared around the time of DirectX installationAffected if Unexpected services with elevated privileges exist that were not present before
-
Review security/event logs for installer executionOpen Event Viewer and check Security logs for Event ID 4688 (Process Creation) showing dxwebsetup.exe or DirectX installer running with high integrity levelAffected if Log entries show the DirectX installer executed with HIGH integrity
A user is affected if the DirectX End-User Runtime Web Installer version 9.29.1974.0 was run on a system where standard users have write access to %TEMP%, and any unauthorized services or suspicious executables appear in the TEMP folder or service list.
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.
From vendor dataSince Microsoft disputes this as a vulnerability, apply compensating controls: restrict TEMP folder write permissions, implement application whitelisting, monitor for unauthorized service creation, and consider running installers in isolated environments with admin privileges only when necessary.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68623 — 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-68623 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