Security Resilience

CVE-2024-12251

Command Injection in Progress Telerik Ui For Winui 2.0.0 – 3.0.0

Published
12 February 2025
Modified
21 May 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0052 43th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-12251 is a high-severity Command Injection (CWE-77) vulnerability in Progress Telerik Ui For Winui. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-12251 is a command injection vulnerability (CWE-77) in Progress Telerik UI for WinUI versions prior to 2025 Q1 (3.0.0), caused by improper neutralization of hyperlink elements. Published on 2025-02-12, it carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact on affected systems.

A local attacker with no privileges can exploit this vulnerability by tricking a user into interacting with a malicious hyperlink, such as clicking it in a UI context. Successful exploitation enables command injection, allowing the attacker to achieve high levels of confidentiality, integrity, and availability impacts on the targeted system.

The Telerik security advisory at https://docs.telerik.com/devtools/winui/security/kb-security-command-injection-cve-2024-12251 provides details on mitigation, with the fix available in version 2025 Q1 (3.0.0) and later. Security practitioners should ensure upgrades for affected installations.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In Progress Telerik UI for WinUI versions prior to 2025 Q1 (3.0.0), a command injection attack is possible through improper neutralization of hyperlink elements.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-7840Same vendor: Progress
CVE-2026-3519Same vendor: Progress
CVE-2026-3517Same vendor: Progress
CVE-2026-8037Same vendor: Progress
CVE-2026-3518Same vendor: Progress
CVE-2026-4048Same vendor: Progress
CVE-2024-4884Same vendor: Progress
CVE-2024-4883Same vendor: Progress
CVE-2026-65937Same vendor: Progress
CVE-2026-9190Same vendor: Progress

Affected Assets

progress
telerik ui for winui
2.0.0 — 3.0.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References