CVE-2026-129883 in Dashboardinfo

Summary

by MITRE • 11/16/2026

thirdweb Dashboard through commit 940b3745 contains an open redirect vulnerability that allows remote attackers to send users to arbitrary sites by supplying an unvalidated redirectUri parameter on the /pay/[id] payment link page. Attackers can distribute payment links with a malicious redirectUri that PayPageWidget opens via window.open after payment without noopener, enabling phishing and reverse tabnabbing of the payment page.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/16/2026

The vulnerability identified in thirdweb Dashboard prior to commit 940b3745 represents a critical web security flaw classified as an open redirect with significant implications for user safety and data integrity. This issue specifically affects the /pay/[id] payment link functionality, where the application accepts a redirectUri parameter from external inputs without performing adequate validation or sanitization checks. In standard secure development practices, any URL provided by users that dictates post-action navigation must be strictly validated against an allowlist of trusted domains to prevent manipulation. The absence of such controls allows remote attackers to craft malicious payment links containing arbitrary URLs within the redirectUri field. When a victim interacts with these compromised links and completes the associated transaction or action, the application blindly redirects them to the attacker-controlled destination rather than a legitimate confirmation page.

The operational impact of this vulnerability extends beyond simple misdirection due to the specific implementation details involving the PayPageWidget component. Upon completion of the payment process, the widget utilizes window.open to display the redirect target in a new browser tab or window. Crucially, this invocation fails to include noopener and noreferrer attributes in the HTML anchor tag or JavaScript call. The omission of noopener is particularly dangerous as it establishes a reference relationship between the newly opened page and the original payment page via the window.opener property. This technical oversight enables reverse tabnabbing attacks, where the malicious third-party site can programmatically access properties of the parent window, including its location object. If the user remains logged into their thirdweb dashboard or other sensitive web applications in the same browser session, the attacker-controlled page could potentially redirect the original payment page to a phishing site that mimics the legitimate interface, thereby tricking the victim into entering credentials or sensitive financial information on the fake login screen while believing they are still on the secure platform.

Furthermore, this vulnerability facilitates traditional phishing campaigns by allowing attackers to seamlessly transition users from a trusted domain to an untrusted one immediately after a high-trust action like payment completion. Users often lower their guard after completing a transaction, assuming the process is finished and safe. By exploiting this psychological state through open redirect mechanics, adversaries can deploy sophisticated social engineering attacks that appear legitimate due to the initial trust established by the thirdweb domain. This aligns with Common Weakness Enumeration (CWE) standards under CWE-601, which defines URL Redirection to Untrusted Site as a weakness where an application redirects users to external sites without proper validation of the target destination. Additionally, the failure to set noopener relates closely to CWE-1022, specifically regarding missing security attributes that prevent malicious pages from accessing parent window objects, thereby facilitating reverse tabnabbing scenarios documented in various web security guidelines.

From a threat intelligence perspective, this vulnerability maps directly to techniques observed in real-world attacks as described by the MITRE ATT&CK framework. The ability to redirect users corresponds to T1566.002, which involves Spearphishing via Link Injection, where attackers embed malicious URLs into legitimate-looking links to deceive victims. The exploitation of window.opener for reverse tabnabbing is a known tactic used in credential harvesting and session hijacking attempts, often categorized under initial access or persistence strategies depending on the ultimate goal of the attacker. Security researchers have long highlighted that open redirects are rarely isolated issues but rather gateways to more severe compromises when combined with missing security headers like noopener. The combination of these factors creates a high-risk environment where user data and session integrity are directly compromised by simple URL manipulation.

To mitigate this vulnerability, immediate remediation steps must focus on implementing strict input validation for the redirectUri parameter. Developers should enforce an allowlist approach, ensuring that only pre-approved domains can be used as redirection targets. Any attempt to use external or unverified URLs should result in a default safe fallback page rather than executing the redirect. Additionally, it is imperative to update all instances of window.open calls associated with user-controlled destinations to include noopener and noreferrer attributes. This change severs the reference between the new tab and the parent window, effectively neutralizing reverse tabnabbing attacks regardless of whether an open redirect exists. Code reviews should also be conducted to identify other potential entry points for similar vulnerabilities across the dashboard interface. Regular security testing using automated scanners that specifically check for open redirects and missing noopener attributes will help maintain a robust defense posture against these persistent web-based threats.

Responsible

VulnCheck

Reservation

11/16/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!