dbcve.org
Telerik Ui For WinformsApplication · Progress

CVE-2025-0332

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 2025.1.211 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Progress® Telerik® UI for WinForms, versions prior to 2025 Q1 (2025.1.211), using the improper limitation of a target path can lead to decompressing an archive's content into a restricted directory.

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 confidence

Telerik UI for WinForms contains a path traversal vulnerability in its archive decompression functionality. The application fails to properly validate or restrict target paths during extraction, allowing an attacker to write archive contents to arbitrary directories on the system through specially crafted archive files.

MitigationUpgrade to Telerik UI for WinForms version 2025.1.211 (2025 Q1) or later to obtain the patch for this vulnerability.

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
Telerik Ui For WinformsApplication
Affected:< 2025.1.211

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Telerik UI for WinForms assemblies
    Search the application bin directory and system GAC for Telerik.WinForms.UI.dll or similar Telerik assemblies. On typical Windows systems, check paths like C:\Program Files\Telerik\ or the application's bin folder.
    Affected if Telerik UI for WinForms assemblies are present in the environment
  2. Determine the installed Telerik version
    Right-click the Telerik.WinForms.UI.dll file, select Properties, then view the Details tab for Product Version. Alternatively, query the assembly version programmatically via PowerShell: [System.Diagnostics.FileVersionInfo]::GetVersionInfo('path\to\Telerik.WinForms.UI.dll').ProductVersion
    Affected if The version number is lower than 2025.1.211 (e.g., 2024.3.1125, 2024.2.512, etc.)
  3. Identify if archive extraction is used
    Search application source code for usages of RadZipArchive, ZipPackage, or Telerik's compression-related classes. Check for patterns like '.Extract', 'ZipFile.Extract', or custom archive handling code that processes user-supplied or downloaded archives.
    Affected if The application uses any Telerik or .NET archive extraction functionality to decompress zip files from untrusted sources
  4. Verify extraction destination validation
    Review the archive extraction code to determine if path traversal validation exists. Look for checks that ensure extracted files remain within a designated root directory, such as checking if the destination path starts with the extraction root path.
    Affected if No path validation is performed before extraction, or the validation can be bypassed by using path traversal sequences (e.g., ../../../') in archive entry names

The environment is affected if Telerik UI for WinForms version lower than 2025.1.211 is installed AND the application extracts archives from potentially untrusted sources without validating that extracted file paths stay within the intended destination directory.

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 2025.1.211 or later
Fixed in 2025.1.211
Interim mitigation

Upgrade to Telerik UI for WinForms version 2025.1.211 (2025 Q1) or later to obtain the patch for this vulnerability.

Recommended fix High confidence

Telerik UI for WinForms 2025.1.211 (2025 Q1 release)

  1. 1. Identify the current version of Telerik UI for WinForms in your project by checking the NuGet package reference or the installed binaries
  2. 2. Download Telerik UI for WinForms version 2025.1.211 or later from the official Telerik website (docs.telerik.com) or via NuGet
  3. 3. Update the NuGet package reference in your project to the fixed version (2025.1.211 or newer)
  4. 4. Rebuild the solution to ensure the updated binaries are incorporated
  5. 5. Test the application to verify the path traversal vulnerability is remediated and functionality remains intact
Caveat Review the release notes for 2025 Q1 for any breaking changes or deprecated features before upgrading

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

Fix this in Telerik Ui For Winforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0332 — 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-0332 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