Skip to content

Mesh Connect JS SDK Vulnerable to Cross Site Scripting via createLink.openLink

High severity GitHub Reviewed Published Sep 22, 2025 in FrontFin/mesh-web-sdk • Updated Sep 22, 2025

Package

npm @meshconnect/web-link-sdk (npm)

Affected versions

< 3.3.2

Patched versions

3.3.2

Description

Summary

The lack of sanitization of URLs protocols in the createLink.openLink function enables the execution of arbitrary JavaScript code within the context of the parent page.

Details

https://github.com/FrontFin/mesh-web-sdk/blob/cf013b85ab95d64c63cbe46d6cb14695474924e7/packages/link/src/Link.ts#L441
The createLink.openLink function takes base64 encoded links, decodes them, and then sets the resulting string as the src attribute of an iframe. It’s important to note that the protocol part is not validated, so a payload, which is a valid URL, such as javascript:alert(document.domain)//, can be provided to the function.

PoC

  1. Extract poc-mesh-web-sdk.zip
  2. Run yarn install and then yarn start
  3. Paste this payload inside the input box: amF2YXNjcmlwdDphbGVydCh3aW5kb3cucGFyZW50LmRvY3VtZW50LmJvZHkuZ2V0RWxlbWVudHNCeVRhZ05hbWUoImgyIikuaXRlbSgwKVsiaW5uZXJIVE1MIl0pLy8=
  4. Click on the OpenLink button
  5. Notice the alert box and ability to access the h2 title from the parent page

It can also be verified via https://paylink.meshconnect.com/?linkToken=amF2YXNjcmlwdDphbGVydCgpLy8=.

Impact

This is technically indistinguishable from a real page at the rendering level and allows access to the parent page DOM, storage, session, and cookies. If the attacker can specify customIframeId, they can hijack the source of existing iframes.

If access to the private key is possible or if transactions are tampered with or initialized, in a wallet context, it can result in a critical impact due to loss of funds scenarios.

Reporters

References

Published by the National Vulnerability Database Sep 22, 2025
Published to the GitHub Advisory Database Sep 22, 2025
Reviewed Sep 22, 2025
Last updated Sep 22, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(9th percentile)

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

CVE ID

CVE-2025-59430

GHSA ID

GHSA-vh3f-qppr-j97f

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.