PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-51684 CleverTap CVE debrief

CVE-2025-51684 is a Cross Site Scripting (XSS) vulnerability in CleverTap Web SDK v1.15.1. The application fails to sanitize untrusted data received via window.postMessage before injecting it into the page DOM, allowing an attacker to execute arbitrary JavaScript in the context of the hosting site. This vulnerability can lead to potential execution of arbitrary JavaScript, compromising user sessions or sensitive data. Defenders should assess exposure and prioritize verification and potential upgrades.

Vendor
CleverTap
Product
Web SDK
CVSS
MEDIUM 6.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-30
Original CVE updated
2026-09-09
Advisory published
2026-07-30
Advisory updated
2026-09-09

Who should care

Defenders responsible for CleverTap Web SDK deployments should assess exposure and prioritize verification and potential upgrades. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the affected product scope and implement necessary security measures.

Why it matters

CVE-2025-51684 is a Cross Site Scripting (XSS) vulnerability in CleverTap Web SDK v1.15.1 that allows an attacker to execute arbitrary JavaScript in the context of the hosting site. Defenders should prioritize verifying exposure and assessing the feasibility of upgrading to a fixed version.

  • Potential execution of arbitrary JavaScript in the context of the hosting site
  • Possible compromise of user sessions or sensitive data
  • Required verification of CleverTap Web SDK version in use
  • Potential need for additional security measures to prevent XSS attacks

Technical summary

The CleverTap Web SDK v1.15.1 is vulnerable to Cross Site Scripting (XSS) due to improper sanitization of untrusted data received via window.postMessage before injecting it into the page DOM. This allows an attacker to execute arbitrary JavaScript in the context of the hosting site, potentially leading to compromise of user sessions or sensitive data. The vulnerability has a CVSS score of 6.1 and a severity of MEDIUM. Defenders should prioritize verifying exposure of CleverTap Web SDK v1.15.1 in their environments and assess the feasibility of upgrading to a fixed version.

Defensive priority

Defenders should prioritize verifying exposure of CleverTap Web SDK v1.15.1 in their environments and assess the feasibility of upgrading to a fixed version.

Recommended defensive actions

  • Verify exposure of CleverTap Web SDK v1.15.1 in your environment
  • Assess the feasibility of upgrading to a fixed version
  • Implement additional security measures to prevent XSS attacks
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. A GitHub issue in the CleverTap repository explicitly discusses the vulnerability in CleverTap Web SDK v1.15.1.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-51684 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-51684

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-51684 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-51684

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.