dbcve.org
Ui For WpfApplication · Telerik

CVE-2024-7679

HIGH · 7.8 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 2024.3.924 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 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 confidence

A command injection vulnerability exists in Telerik UI for WinForms versions prior to 2024 Q3 (2024.3.924) due to improper neutralization of hyperlink elements. An attacker can inject malicious commands through hyperlinks, potentially executing arbitrary commands on the target system.

MitigationUpgrade Telerik UI for WinForms to version 2024 Q3 (2024.3.924) or later to remediate the command injection vulnerability. Review all hyperlink-handling code paths in applications using this component.

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
Ui For WpfApplication
Affected:< 2024.3.924

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
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed Telerik UI for WPF version
    Check your project references, NuGet packages, or bin directory for Telerik UI assemblies (Telerik.Windows.*.dll) and note the version number. Also check the csproj or packages.config file for the installed Telerik package version.
    Affected if The installed version is lower than 2024.3.924 (any version prior to 2024 Q3)
  2. Confirm hyperlink handling is in use
    Search your codebase for usages of Telerik hyperlink-related controls or components, such as RadHyperLink, HyperlinkButton, or any custom hyperlink rendering that utilizes Telerik UI rendering methods.
    Affected if Hyperlink controls or hyperlink rendering features from Telerik UI are implemented in the application
  3. Identify hyperlink event handlers
    Review event handlers that process hyperlink clicks or navigate events within Telerik UI controls. Look for event binding patterns involving navigation or URL processing.
    Affected if Code exists that processes hyperlink navigation events from Telerik components
  4. Check for user-supplied hyperlink input
    Inspect application code paths where hyperlinks may be constructed from user input, database content, or external data sources that could be tampered with.
    Affected if Hyperlinks are dynamically generated from external or user-controllable data sources

You are affected if Telerik UI for WPF version is below 2024.3.924 AND your application processes hyperlinks using Telerik UI components, particularly those that could accept maliciously crafted hyperlink values.

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

Upgrade Telerik UI for WinForms to version 2024 Q3 (2024.3.924) or later to remediate the command injection vulnerability. Review all hyperlink-handling code paths in applications using this component.

Recommended fix High confidence

2024.3.924 (2024 Q3) or later

  1. 1. Identify the current version of Telerik UI for WinForms (or WPF) in your project by checking the NuGet package reference or project references
  2. 2. Download or update to Telerik UI for WinForms version 2024.3.924 or later (2024 Q3 release)
  3. 3. Update the NuGet package reference in your project file or package manager: `Update-Package Telerik.WinControls.UI` to the latest version
  4. 4. Rebuild and test the application to ensure the command injection vulnerability in hyperlink handling is resolved
  5. 5. Verify that the hyperlink elements in your application no longer allow arbitrary command execution
Caveat Review Telerik release notes for any breaking changes between your current version and 2024.3.924 before upgrading

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

Fix this in Ui For Wpf Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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