Skip to content

CVE-2017-11357

Progress Telerik UI for ASP.NET AJAX before R2 2017 SP2 does not properly restrict user input to RadAsyncUpload, which allows remote attackers to perform arbitrary file uploads or execute arbitrary code.

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 26 Jan 2023CISA deadline for US federal agencies: 16 Feb 2023known use in ransomware campaignspublic exploit code
EPSS
77.7%chance of exploitation in the next 30 daystop 0.5% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
23 Aug 2017analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • progress:telerik_ui_for_asp.net_ajax

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Unrestricted file upload: a WAF can filter file names and extensions, but it cannot judge what the uploaded file will do.

Also consider: MIME sniff · sandbox storage

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 26 Jan 2023. Known use in ransomware campaigns.
CISA due date
16 Feb 2023, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 1 on Exploit-DB
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 22 Jan 2021 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 23 Aug 2017Published
  2. 24 Jan 2018First public exploit or proof of concept153 days (about 5 months) later
  3. 22 Jan 2021CISA SSVC assessment: exploitation active1,094 days (about 3 years) later
  4. 26 Jan 2023Added to CISA KEV (exploited in the wild)734 days (about 2 years) later
  5. 16 Feb 2023CISA remediation due date (US federal agencies)21 days later
  6. 14 Aug 2026CVE record last updated1,275 days (about 3 years) later
  7. 12 Nov 2026Analysed by vulneraibility.com90 days (about 3 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2017-11357 being exploited?

Yes. CVE-2017-11357 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2017-11357?

CVE-2017-11357 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-11357?

Yes. A fix has been recorded for CVE-2017-11357. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2017-11357 affect?

CVE-2017-11357 affects progress:telerik_ui_for_asp.net_ajax. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Exploits (1)

Other links (2)

  • telerik.com /support/kb/aspnet-ajax/upload-%28async%29/details/insecure-direct-object-refere
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-11357

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com