Skip to main content
VulnerabilityPublished

CVE-2026-26861: clevertap-web-sdk · Origin Validation Error

Affects clevertap-web-sdkSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubclevertap/clevertap-web-sdkpkg:github/clevertap/clevertap-web-sdkOther threatsAffected
  • <=1.15.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-26861, organizations should first verify if their web applications use CleverTap Web SDK version 1.15.2 or earlier. If so, they should seek an updated SDK version from CleverTap that addresses the origin validation flaw or apply vendor-provided patches once available. In the absence of an official patch, developers should implement strict origin validation by replacing the includes() method with exact origin matching, such as using strict equality checks against a whitelist of trusted origins. Additionally, web applications should employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Developers can also sanitize and validate all inputs and messages received via postMessage to ensure they conform to expected formats. Monitoring and logging postMessage events can help detect suspicious activity. Finally, educating development teams about secure handling of cross-origin communications and conducting regular security code reviews focused on message handling functions will help prevent similar vulnerabilities.

Description

CleverTap Web SDK version 1.15.2 and earlier is vulnerable to Cross-Site Scripting (XSS) via window.postMessage. The handleCustomHtmlPreviewPostMessageEvent function in src/util/campaignRender/nativeDisplay.js performs insufficient origin validation using the includes() method, which can be bypassed by an attacker using a subdomain

References

Community reviews

Loading reviews…