CVE-2025-24479
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 · uneditedA Local Code Execution Vulnerability exists in the product and version listed above. The vulnerability is due to a default setting in Windows and allows access to the Command Prompt as a higher privileged user.
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 confidenceThis is a local privilege escalation vulnerability in Windows where a default configuration setting allows an attacker to access the Command Prompt (cmd.exe) with elevated privileges. The vulnerability enables a lower-privileged user to execute code as a higher-privileged account, likely through a Windows service, scheduled task, or system component that runs with elevated permissions and can be exploited to spawn a command shell.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Windows version and buildRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the Windows version and build numberAffected if Running an unpatched Windows version where the vulnerable configuration exists by default
-
Check for unprivileged command prompt access pathsReview installed Windows services, scheduled tasks, and startup programs for configurations that allow launching cmd.exe. Use 'schtasks /query /fo LIST /v' and check service configurations via 'sc qc <service_name>' for any that run with elevated privileges and expose command executionAffected if A service, scheduled task, or component runs with elevated privileges and can be manipulated by a low-privileged user to spawn cmd.exe
-
Audit UAC policy settingsCheck registry key 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System' for UAC-related values such as 'EnableLUA', 'ConsentPromptBehaviorAdmin', and 'LocalAccountTokenFilterPolicy'Affected if UAC is disabled or configured to allow token elevation for standard users without proper consent prompts
-
Verify privilege boundaries for built-in administrative toolsUse 'whoami /all' to list current user privileges and group memberships. Check if the current user has SeImpersonatePrivilege or similar privileges that could be leveraged for privilege escalationAffected if A low-privileged user account possesses misconfigured privileges that allow impersonation or spawning elevated processes
A user is affected if their Windows system has a default configuration allowing an unprivileged account to invoke cmd.exe with elevated rights through a service, scheduled task, or system component.
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 dataHarden the affected Windows default settings by restricting or disabling the pathway that allows unprivileged users to invoke cmd.exe with elevated rights; review Windows service configurations, scheduled tasks, and UAC policies to ensure proper privilege boundaries.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24479 — 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-24479 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