🟡 CVE-2025-7074: A vulnerability classified as ... 🟡 CVE-2023-50786: Dradis through 4.16.0 allows r... 🟡 CVE-2025-47228: In the Production Environment ... ⚠️ CVE-2025-47227: In the Production Environment ... 🟡 CVE-2025-53605: The protobuf crate before 3.7.... 🟡 CVE-2025-53604: The web-push crate before 0.10... ⚠️ CVE-2025-53603: In Alinto SOPE SOGo 2.0.2 thro... ⚠️ CVE-2025-43711: Tunnelblick 3.5beta06 before 7... 🔥 CVE-2025-26850: The agent in Quest KACE System... 🔥 CVE-2025-48952: NetAlertX is a network, presen... 🟡 CVE-2025-7070: A vulnerability has been found... ⚠️ CVE-2025-53366: The MCP Python SDK, called `mc... ⚠️ CVE-2025-53365: The MCP Python SDK, called `mc... 🟡 CVE-2025-7069: A vulnerability, which was cla... 🟡 CVE-2025-7068: A vulnerability, which was cla... 🟡 CVE-2025-53602: Zipkin through 3.5.1 has a /he... 🟡 CVE-2025-7067: A vulnerability classified as ... 🟡 CVE-2025-52497: Mbed TLS before 3.6.4 has a PE... ⚠️ CVE-2025-52496: Mbed TLS before 3.6.4 has a ra... 🟡 CVE-2025-49601: In MbedTLS 3.3.0 before 3.6.4,... 🟡 CVE-2025-49600: In MbedTLS 3.3.0 before 3.6.4,... ⚠️ CVE-2025-46733: OP-TEE is a Trusted Execution ... 🟡 CVE-2025-7061: A vulnerability was found in I... ⚠️ CVE-2025-49809: mtr through 0.95, in certain p... 🟡 CVE-2025-48172: CHMLib through 2bef8d0, as use... 🟡 CVE-2025-7066: Jirafeau normally prevents bro... 🟡 CVE-2025-6740: The Contact Form 7 Database Ad... 🟡 CVE-2025-6056: Timing difference in password ... 🔥 CVE-2025-52833: Improper Neutralization of Spe... 🔥 CVE-2025-52832: Improper Neutralization of Spe... 🔥 CVE-2025-52831: Improper Neutralization of Spe... 🔥 CVE-2025-52830: Improper Neutralization of Spe... ⚠️ CVE-2025-52828: Deserialization of Untrusted D... ⚠️ CVE-2025-52813: Missing Authorization vulnerab... ⚠️ CVE-2025-52807: Improper Control of Filename f... ⚠️ CVE-2025-52805: Path Traversal vulnerability i... ⚠️ CVE-2025-52798: Improper Neutralization of Inp... ⚠️ CVE-2025-52796: Improper Neutralization of Inp... ⚠️ CVE-2025-52776: Improper Neutralization of Inp... ⚠️ CVE-2025-52718: Improper Control of Generation... 🟡 CVE-2025-50039: Missing Authorization vulnerab... 🟡 CVE-2025-50032: Missing Authorization vulnerab... ⚠️ CVE-2025-4414: Improper Control of Filename f... ⚠️ CVE-2025-49870: Improper Neutralization of Spe... 🔥 CVE-2025-49867: Incorrect Privilege Assignment... ⚠️ CVE-2025-49866: Improper Neutralization of Inp... 🟡 CVE-2025-49431: Missing Authorization vulnerab... ⚠️ CVE-2025-49418: Server-Side Request Forgery (S... 🔥 CVE-2025-49417: Deserialization of Untrusted D... 🔥 CVE-2025-49414: Unrestricted Upload of File wi... 🟡 CVE-2025-49303: Improper Limitation of a Pathn... 🔥 CVE-2025-49302: Improper Control of Generation... ⚠️ CVE-2025-49274: Improper Neutralization of Inp... ⚠️ CVE-2025-49247: Improper Neutralization of Inp... ⚠️ CVE-2025-49245: Improper Neutralization of Inp... ⚠️ CVE-2025-49070: Improper Control of Filename f... 🟡 CVE-2025-48231: Improper Neutralization of Inp... 🟡 CVE-2025-47634: Missing Authorization vulnerab... ⚠️ CVE-2025-47627: Improper Control of Filename f... 🟡 CVE-2025-47565: Missing Authorization vulnerab... 🟡 CVE-2025-47479: Weak Authentication vulnerabil... ⚠️ CVE-2025-39487: Improper Neutralization of Inp... ⚠️ CVE-2025-32311: Improper Neutralization of Inp... ⚠️ CVE-2025-32297: Improper Neutralization of Spe... ⚠️ CVE-2025-31037: Improper Neutralization of Inp... 🔥 CVE-2025-30933: Unrestricted Upload of File wi... 🔥 CVE-2025-28983: Improper Neutralization of Spe... ⚠️ CVE-2025-28980: Improper Limitation of a Pathn... ⚠️ CVE-2025-28978: Improper Neutralization of Inp... 🟡 CVE-2025-28976: Improper Neutralization of Inp... ⚠️ CVE-2025-28968: Improper Neutralization of Inp... ⚠️ CVE-2025-24780: Improper Neutralization of Spe... ⚠️ CVE-2025-24771: Improper Neutralization of Inp... 🔥 CVE-2025-23970: Incorrect Privilege Assignment... 🟢 CVE-2025-7060: A vulnerability was found in M... 🟡 CVE-2025-5351: A flaw was found in the key ex... 🟡 CVE-2025-53569: Cross-Site Request Forgery (CS... 🟡 CVE-2025-53568: Cross-Site Request Forgery (CS... 🟡 CVE-2025-53566: Improper Neutralization of Inp... 🟡 CVE-2025-30983: Improper Neutralization of Inp... ⚠️ CVE-2025-30979: Improper Neutralization of Spe... ⚠️ CVE-2025-30969: Improper Neutralization of Spe... ⚠️ CVE-2025-30947: Improper Neutralization of Spe... 🟡 CVE-2025-30943: Improper Neutralization of Inp... 🟡 CVE-2025-30929: Missing Authorization vulnerab... 🟡 CVE-2025-29012: Missing Authorization vulnerab... 🟡 CVE-2025-29007: Missing Authorization vulnerab... 🟡 CVE-2025-29001: Missing Authorization vulnerab... 🟡 CVE-2025-28971: Improper Neutralization of Inp... ⚠️ CVE-2025-28969: Improper Neutralization of Spe... ⚠️ CVE-2025-28967: Improper Neutralization of Spe... 🟡 CVE-2025-28963: Server-Side Request Forgery (S... 🟡 CVE-2025-28957: Improper Neutralization of Inp... 🔥 CVE-2025-28951: Unrestricted Upload of File wi... 🟡 CVE-2025-27358: Improper Neutralization of Scr... 🟡 CVE-2025-27326: Improper Neutralization of Inp... 🟡 CVE-2025-26591: Improper Neutralization of Inp... 🟡 CVE-2025-24764: Improper Neutralization of Inp... 🟡 CVE-2025-24757: Improper Neutralization of Inp... ⚠️ CVE-2025-24748: Improper Neutralization of Spe...
New "DoubleClickjacking" Exploit Bypasses Clickjacking Protections

New "DoubleClickjacking" Exploit Bypasses Clickjacking Protections

Published on January 6, 2025

Author: Cybersecurity News Desk

A novel cybersecurity threat, termed "DoubleClickjacking," has emerged, posing significant risks to web users and developers alike. This advanced form of clickjacking manipulates the brief interval between two clicks in a double-click sequence, effectively bypassing traditional security measures such as X-Frame-Options and SameSite cookies.

Understanding DoubleClickjacking

Traditional clickjacking involves deceiving users into clicking on concealed or disguised web elements, leading to unintended actions like malware installation or unauthorized information disclosure. DoubleClickjacking elevates this threat by exploiting the timing gap between two clicks in a double-click, allowing attackers to perform malicious actions without user awareness.

Mechanism of the Attack

The attack typically unfolds as follows:

  1. An attacker-controlled website opens a new browser window or tab, often mimicking legitimate prompts such as CAPTCHA verifications.
  2. The user is prompted to double-click to proceed.
  3. During the double-click, the parent site utilizes JavaScript to redirect to a malicious page, such as an OAuth authorization request.
  4. The top window closes, and the user's second click unknowingly approves the malicious action on the parent site.

This method requires minimal user interaction, making it highly deceptive and effective.

Implications and Risks

DoubleClickjacking can lead to severe consequences, including:

  • Unauthorized account access through malicious OAuth authorizations.
  • Unintended changes to account settings, potentially disabling security features.
  • Exploitation of browser extensions, such as crypto wallets or VPNs, leading to unauthorized transactions or data exposure.

Mitigation Strategies

To defend against DoubleClickjacking, consider the following measures:

Client-Side Protections

Implement JavaScript solutions that disable critical buttons by default, enabling them only upon detecting intentional user interactions like mouse movements or key presses. For example:


(function(){
    if (window.matchMedia && window.matchMedia("(hover: hover)").matches) {
        var buttons = document.querySelectorAll('form button, form input[type="submit"]');
        buttons.forEach(button => button.disabled = true);
        function enableButtons() {
            buttons.forEach(button => button.disabled = false);
        }
        document.addEventListener("mousemove", enableButtons);
        document.addEventListener("keydown", e => {
            if(e.key === "Tab") enableButtons();
        });
    }
})();

This script ensures that buttons remain disabled until real user activity is detected, thwarting automated or tricked clicks.

Browser-Level Solutions

Advocate for the development of new browser standards to prevent rapid context-switching during double-click sequences. Potential measures include introducing a Double-Click-Protection HTTP header or enhancing Content Security Policy (CSP) directives to account for multi-click scenarios.

Best Practices for Developers

  • Incorporate protective scripts into sensitive pages, such as those handling OAuth permissions or payment confirmations.
  • Enforce stricter controls over embedded windows or opener-based navigation to prevent unauthorized UI manipulations.

Conclusion

DoubleClickjacking represents a new frontier in web-based attacks, exploiting timing vulnerabilities in user interactions to bypass established clickjacking defenses. Developers and security teams must act swiftly to address this risk by implementing client-side protections and advocating for browser-level security enhancements. As the digital landscape evolves, staying vigilant against innovative attack methods like DoubleClickjacking is essential to safeguarding user data and trust.

Source: New "DoubleClickjacking" Exploit Bypasses Clickjacking Protections on Major Websites.

Back to Posts
// This is the updated banner script block with corrected ID selectors