Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach public PivotGrid filter input
-
DeliveryCraft malicious MDX/XML filter value
-
ExploitInject into XMLA SOAP request
-
ExecutionAlter MDX predicate server-side
-
ImpactExfiltrate unauthorized cube data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
|
| Exploitation Conditions | Exploitation requires the target application to use the Kendo UI for jQuery PivotGrid component configured with the XMLA transport pointing at a backend XMLA/OLAP data source (e.g., Microsoft SQL Server Analysis Services); the attacker supplies crafted filter values that are passed into MDX predicates or SOAP XML. Applications that do not use the PivotGrid, or that use PivotGrid with a non-XMLA (local/flat) data source, are not affected. Limiting factors: the PivotGrid filter surface must be reachable by the attacker (its exposure to unauthenticated users depends on the host application's own access controls), and the affected version must be prior to v2026.3.1015. No user interaction by a victim is required (UI:N). |
| Impact | The vendor CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5 HIGH) signals a network-reachable, low-complexity, unauthenticated injection whose impact is confidentiality-only (C:H, I:N, A:N) - consistent with the CWE-74 injection class and the description's emphasis on data exposure via the configured XMLA connection rather than code execution or tampering. However, the raw CVSS understates a critical gating factor: exploitation is not possible against a default Kendo UI deployment - it requires an application that specifically uses the PivotGrid component wired to an XMLA (SSAS/OLAP) transport, so the real-world exploitable population is a subset of all Kendo UI installs. No EPSS score, CISA KEV listing, POC, or SSVC decision data was provided, so exploitation probability and automatability cannot be quantified from the input. There is no conflict between the signals, but there is a MISSING-data gap: the PR:N 'unauthenticated' rating is believable for a public-facing PivotGrid filter, yet whether a given deployment exposes the PivotGrid to unauthenticated users depends on the host application's access controls - verify per deployment. Net: a credible, vendor-confirmed data-disclosure flaw worth patching promptly for anyone using PivotGrid+XMLA, but likely narrower in real-world reach than the 7.5 score alone implies. |
| Exploit ScenarioDerived | An attacker interacting with a web application that embeds a Kendo UI PivotGrid backed by an XMLA/SSAS data source submits specially crafted filter values that break out of the intended MDX predicate or inject XML markup into the SOAP request sent to the XMLA endpoint. The manipulated query returns cube data the user was never authorized to see, exposing information reachable through the configured XMLA connection. No public exploit code was identified at time of analysis, and the low attack complexity (AC:L) means manipulation requires only crafted filter input, not special timing or conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Remote, unauthenticated injection in the Progress Kendo UI for jQuery PivotGrid XMLA transport (all versions prior to v2026.3.1015) lets an attacker place crafted filter values into MDX predicates and the surrounding SOAP request body, altering the query issued to a backend XMLA/OLAP data source such as Microsoft SQL Server Analysis Services. The assessed impact is confidentiality-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5 HIGH) - data reachable through the configured XMLA connection may be read or exposed, but integrity and availability of the source are not affected. Only applications that render PivotGrid with the XMLA transport enabled and a reachable OLAP backend are exposed; no public exploit was identified at time of analysis and the issue is not confirmed as actively exploited.
RemediationAI
Upgrade to Kendo UI for jQuery v2026.3.1015 or later - this is the vendor-released fixed version referenced in the advisory at https://www.telerik.com/kendo-jquery-ui/documentation/knowledge-base/kb-security-pivotgrid-mdx-soap-injection-cve-2026-108116; rebuild and redeploy any bundled/copied Kendo assets so cached older scripts are not still served. If an immediate upgrade is not possible, apply compensating controls that accept trade-offs: enforce authentication and authorization on the server-side endpoint that receives PivotGrid filter parameters and rejects or sanitizes MDX/SOAP metacharacters (note this duplicates the missing fix and must be maintained as filter syntax evolves); run the XMLA connection under a least-privilege OLAP account restricted to the specific cubes and measures the dashboard legitimately needs, which limits what injected predicates can reach but does not remove the injection; if OLAP federation is not essential, switch PivotGrid to a local/flat data source or disable the XMLA transport, understanding that this removes live multidimensional querying; and restrict network access to the XMLA endpoint so only the application server can reach it, which reduces exposure from direct attackers but not from abuse through the application itself. A WAF rule targeting anomalous MDX/SOAP payloads in filter parameters can add monitoring value but is bypassable and should not be treated as a fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Kendo UI for jQuery PivotGrid is a client-side data-visualization widget; its XMLA transport builds SOAP requests over HTTP that carry MDX (Multidimensional Expressions) queries to an OLAP engine such as Microsoft SQL Server Analysis Services or another XMLA-compliant backend. Because user-supplied filter values are not properly neutralized before being interpolated into MDX predicate expressions and the XML body of the SOAP envelope, the flaw falls into CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component, i.e., generic injection). An attacker who controls a filter value can therefore reshape the MDX WHERE/predicate logic (e.g., broadening or redirecting the slice of the cube that is queried) or inject XML markup into the SOAP message itself. The injected query executes with the privileges of the XMLA connection's configured credentials, so the practical blast radius is bounded by what that connection can read on the OLAP server - which is why the vendor-assessed vector scores confidentiality as High (C:H) while leaving integrity and availability unaffected (I:N/A:N). Whether the injection point is reachable without authentication depends on the host application's own access controls around the PivotGrid endpoint, even though the CVSS vector (PR:N) records the component-level injection as unauthenticated and requiring no victim interaction (UI:N).
Know when Kendo Ui For Jquery gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-reachable PivotGrid filter input with no auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is unauthorized data disclosure via the XMLA connection (C:H), with no stated integrity or availability effect.
Primary rating from Vendor (ProgressSoftware).
CVSS VectorVendor: ProgressSoftware
Lifecycle Timeline
2DescriptionCVE.org
In Progress Kendo UI for jQuery prior to v2026.3.1015, specially crafted filter values in the PivotGrid XMLA transport could alter MDX predicates or inject XML markup into SOAP requests, potentially exposing data accessible through the configured XMLA connection.
Executive ViewAI
Progress Kendo UI for jQuery PivotGrid deployments that use the XMLA transport to connect to an OLAP backend can be manipulated by an unauthenticated remote attacker, potentially exposing business intelligence data held in cubes such as Microsoft SQL Server Analysis Services. Impact is limited to confidentiality - an attacker could read data the application's XMLA connection is permitted to reach - but no integrity or availability loss to the underlying data source is expected. Leadership should care because affected systems are internet-facing analytics dashboards, and exposed OLAP content may include financial, customer, or strategic reporting data; exposure is confined to organizations that have enabled the XMLA transport against a reachable backend.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the PivotGrid XMLA transport where the feature is not required; block or allowlist network reachability from application servers to OLAP/XMLA backends; run the XMLA connection under a least-privileged, read-only service account restricted to the cubes in use; validate or allowlist client-supplied filter values server-side before they reach MDX predicates; and deploy WAF and log-based detection for XMLA/SOAP injection patterns and anomalous cube queries.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Kendo Ui For Jquery
View allCross-site scripting in the Kendo UI for jQuery FileBrowser and ImageBrowser components (v2023.1.117 through pre-v2026.3
Cross-site scripting in Progress Kendo UI for jQuery (versions prior to 2026.3.1015) allows an attacker to execute JavaS
Cross-site scripting in Progress Kendo UI for jQuery's Validator affects versions from 2012.2.710 through 2026.3.1015, w
Cross-site scripting in Progress Kendo UI for jQuery (all versions prior to 2026.3.1015) allows an authenticated low-pri
Cross-site scripting (DOM/stored) in Progress Kendo UI for jQuery prior to v2026.3.1015 allows an attacker who can influ
Cross-site scripting in Progress Kendo UI for jQuery prior to 2026.3.1015 allows an authenticated attacker with low priv
Stored cross-site scripting in the Progress Kendo UI for jQuery ListBox widget allows an attacker who can modify the dat
Cross-site scripting in Progress Kendo UI for jQuery (releases from v2020.1.114 through 2026.3.1015) lets an attacker wh
Prototype pollution in Progress Kendo UI for jQuery versions prior to 2026.3.1015 lets an authenticated, low-privileged
Cross-site scripting in Progress Kendo UI for jQuery (versions 2022.3.1109 up to but not including 2026.3.1015) allows a
Stored/DOM cross-site scripting in Progress Kendo UI for jQuery (Scheduler widget, versions 2026.3.811 and earlier) allo
Cross-site scripting (XSS) in the PanelBar component of Progress Kendo UI for jQuery (versions 2019.2.514 through before
EUVD-2026-102080
GHSA-63f7-2qgh-c93c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB