CVE-2025-51684: CleverTap Web SDK v1.15.1 is vulnerable to Cross Site Scripting (XSS).
CleverTap Web SDK v1.15.1 is vulnerable to Cross Site Scripting (XSS). The application does not sanitize untrusted data received via window.postMessage before injecting it into the page DOM. An attacker can craft a malicious message that, when processed by renderCustomHtml, results in execution of arbitrary JavaScript in the context of the hosting site.
Security readout for executives and security teams
Plain-English summary
Websites using CleverTap Web SDK v1.15.1 may execute attacker-supplied JavaScript after processing an untrusted browser message. Successful exploitation could expose limited user data or permit limited unauthorized actions within the hosting site. The published severity is medium, and user interaction is required.
Executive priority
Treat as a prompt, moderate-priority web remediation. Quickly identify internet-facing sites using v1.15.1, then prioritize those with logged-in users or sensitive workflows. Escalate if internal testing confirms reachability or credible exploitation evidence emerges.
Technical view
The SDK passes untrusted window.postMessage data to renderCustomHtml without adequate sanitization before DOM insertion, creating a CWE-79 cross-site scripting condition. The CVSS 3.1 score is 6.1: network-accessible, low complexity, no privileges required, user interaction required, changed scope, and limited confidentiality and integrity impact.
Likely exposure
Exposure is limited to sites deploying CleverTap Web SDK v1.15.1 where the vulnerable message-handling and custom HTML rendering path is reachable. The source bundle does not identify other affected versions, configurations, or products, so broader exposure should not be assumed.
Exploitation context
The supplied sources describe a crafted browser message leading to JavaScript execution in the hosting site's context. They do not establish active exploitation, public weaponization, or inclusion in CISA KEV. The CVSS vector indicates user interaction is necessary.
Researcher notes
The record attributes the flaw to missing sanitization between postMessage input and renderCustomHtml DOM injection. Evidence provided here does not name a fixed version, patch, origin-validation requirement, or complete affected-version range. Researchers should avoid extrapolating beyond v1.15.1 and track the vendor issue for clarification.
Mitigation direction
Inventory public applications and confirm whether CleverTap Web SDK v1.15.1 is deployed.
Check the referenced vendor issue and CVE record for current upgrade or mitigation guidance.
Prioritize affected sites handling authenticated sessions, personal data, or sensitive transactions.
Where operationally feasible, disable the affected integration until vendor-supported remediation is applied.
Validation and detection
Verify deployed frontend assets and dependency records identify the exact CleverTap SDK version.
Determine whether renderCustomHtml and window.postMessage processing are enabled and reachable.
After remediation, confirm untrusted messages cannot cause script execution or unsafe DOM insertion.
Retest affected pages for expected CleverTap functionality and security regressions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.