CVE-2024-7575
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 Progress Telerik UI for WPF versions prior to 2024 Q3 (2024.3.924), a command injection attack is possible through improper neutralization of hyperlink elements.
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 confidenceTelerik UI for WPF versions prior to 2024 Q3 (2024.3.924) contain a command injection vulnerability where hyperlink elements are not properly sanitized, allowing attackers to inject and execute arbitrary system commands through malicious hyperlink input.
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< 2024.3.924CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Telerik UI for WPF assembly versionIn your project, find the Telerik.Windows.Controls or Telerik.Windows.Documents DLL (typically in the /bin folder or referenced via NuGet). Right-click the DLL, select Properties, and view the File Version or Product Version attribute. Alternatively, check the Version field in the NuGet package manager for Telerik.UI.for.Wpf.Affected if The version number is lower than 2024.3.924 (for example, 2024.2.512, 2023.3.1015, etc.)
-
Identify if hyperlink-enabled controls are usedSearch your codebase for usage of Telerik WPF controls that support hyperlinks, such as RadRichTextBox, RadPdfViewer, or any control that renders hyperlink content from external or user-provided sources. Review XAML files and C# code for instances of Hyperlink or RadDocument derivatives.Affected if Hyperlink-rendering controls from Telerik are in use and accept input from untrusted sources
-
Check for unsanitized hyperlink command execution patternsInspect any code that processes or renders hyperlinks from external input (e.g., loaded from files, databases, user input). Look for scenarios where the NavigateUrl or similar hyperlink properties are set directly from external data without validation.Affected if Hyperlinks from external or untrusted sources are rendered without sanitization before the control displays them
-
Verify application attack surfaceReview how your application handles document import or content loading (such as importing HTML, RTF, or PDF documents). Determine if these imported documents could contain malicious hyperlinks that get processed by Telerik WPF controls.Affected if The application imports or displays documents containing hyperlinks from external or untrusted sources
You are affected if your Telerik UI for WPF version is below 2024.3.924 AND your application uses hyperlink-enabled controls that render content from external or untrusted sources without additional sanitization.
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 · scoped2024.3.924
Upgrade Telerik UI for WPF to version 2024.3.924 or later to obtain the patched library with proper hyperlink sanitization.
Telerik UI for WPF 2024.3.924 (2024 Q3) or later
- Obtain Telerik UI for WPF version 2024.3.924 or later from the official Telerik website or NuGet package repository
- Update the Telerik.UI.for.Wpf NuGet package in your project to version 2024.3.924 or newer using NuGet Package Manager or dotnet CLI (e.g., dotnet add package Telerik.UI.for.Wpf --version 2024.3.924)
- Rebuild your application to incorporate the patched libraries
- Test your application's hyperlink functionality to ensure proper behavior after the upgrade
- Verify that the command injection vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7575 — 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-2024-7575 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