Threats / Progress / CVE-2024-4358
CVE-2024-4358
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Progress Telerik Report Server vulnerability
Progress Telerik Report Server contains an authorization bypass vulnerability allowing attackers to spoof authentication and gain unauthorized access to the application.
Verdict
Today item — known-exploited.
An attacker can bypass authorization controls in Telerik Report Server through spoofing techniques, obtaining unauthorized access to sensitive reporting functionality and data without valid credentials.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
457 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-13).
Probability (EPSS)
EPSS 0.97482 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Progress, Telerik Report Server. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-290 Auth Bypass by Spoofing — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request that spoofs authentication credentials or session tokens to bypass authorization checks.
Business
Unauthorized users gain direct access to the report server, exposing confidential business intelligence and operational data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate privileges by impersonating legitimate administrators or service accounts within the application.
Business
Attackers obtain administrative capabilities, enabling modification or deletion of critical reports and system configurations.
3
Lateral reach — past segmentation narrative 3
Attacker
I extract sensitive data from reports and databases accessible through the compromised server instance.
Business
Confidential business metrics, customer information, and financial data are exfiltrated, creating compliance and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by ProgressSoftwareCNA