dbcve.org
Update Package FrameworkApplication · Dell

CVE-2025-22395

HIGH · 7.8 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 22.01.02 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Dell Update Package Framework, versions prior to 22.01.02, contain(s) a Local Privilege Escalation Vulnerability. A local low privileged attacker could potentially exploit this vulnerability, leading to the execution of arbitrary remote scripts on the server. Exploitation may lead to a denial of service by an attacker.

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 confidence

Dell Update Package Framework versions prior to 22.01.02 contain a local privilege escalation vulnerability where a low-privileged local attacker can execute arbitrary remote scripts with elevated privileges. This stems from improper privilege validation in the update framework, allowing script injection and execution beyond intended permissions.

MitigationUpdate Dell Update Package Framework to version 22.01.02 or later to remediate the vulnerability. Prior to patching, restrict local access to trusted users and monitor for suspicious script execution activities.

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
Update Package FrameworkApplication
Affected:< 22.01.02

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Dell Update Package Framework is installed
    Check for Dell Update Package Framework installation by looking in common installation directories such as C:\Program Files\Dell\ or C:\Program Files (x86)\Dell\, or use the Windows Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for installed programs containing 'Dell Update Package Framework' in the display name.
    Affected if The software is present on the system.
  2. Determine the installed version
    Locate the Dell Update Package Framework executable or DLL (typically named DUFramework.exe or similar) and check its file properties for the version number, or query the Windows Registry under the uninstall key for the installed version string.
    Affected if The version number is lower than 22.01.02.
  3. Verify the update framework service is running
    Open Services (services.msc) and check for a Dell Update Package Framework service, or run 'sc query' via command line to enumerate services containing 'Dell' or 'Update' in the name.
    Affected if The Dell Update Package Framework service is present and running.
  4. Check for suspicious script execution logs
    Review Windows Event Logs under Application and Security logs for script execution events (Event ID 4688 for process creation) involving Dell update components executing scripts from unexpected locations, or check for recent creation/modification of scripts in the Dell update framework directories.
    Affected if Scripts are being executed by the update framework from locations outside the expected application directory.

The system is affected if Dell Update Package Framework is installed with a version prior to 22.01.02 and the update framework service or component is actively in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 22.01.02 or later
Fixed in 22.01.02
Interim mitigation

Update Dell Update Package Framework to version 22.01.02 or later to remediate the vulnerability. Prior to patching, restrict local access to trusted users and monitor for suspicious script execution activities.

Recommended fix High confidence

22.01.02

  1. Identify the currently installed version of Dell Update Package Framework
  2. Navigate to Dell's official support website and download Dell Update Package Framework version 22.01.02 or later
  3. Apply the update following Dell's standard installation procedures for the Update Package Framework
  4. Verify the updated version is 22.01.02 or later by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Update Package Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22395 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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