🟡 CVE-2025-3800: A vulnerability has been found... 🟡 CVE-2025-3799: A vulnerability, which was cla... 🟡 CVE-2025-3798: A vulnerability, which was cla... 🟡 CVE-2025-3661: The SB Chart block plugin for ... ⚠️ CVE-2025-3404: The Download Manager plugin fo... 🔥 CVE-2021-4455: The Wordpress Plugin Smart Pro... 🟡 CVE-2025-3797: A vulnerability classified as ... ⚠️ CVE-2025-3809: The Debug Log Manager plugin f... ⚠️ CVE-2025-2111: The Insert Headers And Footers... ⚠️ CVE-2025-3103: The CLEVER - HTML5 Radio Playe... 🟡 CVE-2025-3275: The Themesflat Addons For Elem... 🟡 CVE-2025-1457: The Element Pack Addons for El... 🔥 CVE-2025-1093: The AIHub theme for WordPress ... 🟡 CVE-2025-3284: The User Registration & Member... 🔥 CVE-2025-3278: The UrbanGo Membership plugin ... ⚠️ CVE-2025-2010: The JobWP – Job Board, Job Lis... 🟡 CVE-2025-43903: NSSCryptoSignBackend.cc in Pop... 🟡 CVE-2025-3796: A vulnerability classified as ... ⚠️ CVE-2025-32953: z80pack is a mature emulator o... 🟡 CVE-2025-3795: A vulnerability was found in D... 🟡 CVE-2025-36625: In Nessus versions prior to 10... 🟡 CVE-2025-32377: Rasa Pro is a framework for bu... 🟢 CVE-2025-25985: An issue in Macro-video Techno... 🟡 CVE-2025-25984: An issue in Macro-video Techno... 🟢 CVE-2025-25983: An issue in Macro-video Techno... 🟡 CVE-2025-28355: Volmarg Personal Management Sy... ⚠️ CVE-2025-24914: When installing Nessus to a no... 🟡 CVE-2025-29513: Cross-Site Scripting (XSS) vul... 🟡 CVE-2025-29512: Cross-Site Scripting (XSS) vul... 🟡 CVE-2025-1697: A potential security vulnerabi... 🟡 CVE-2024-41447: A stored cross-site scripting ... 🟡 CVE-2025-32796: Dify is an open-source LLM app... 🟡 CVE-2025-32795: Dify is an open-source LLM app... ⚠️ CVE-2025-32792: SES safely executes third-part... ⚠️ CVE-2025-32442: Fastify is a fast and low over... 🔥 CVE-2025-32434: PyTorch is a Python package th... ⚠️ CVE-2025-32389: NamelessMC is a free, easy to ... 🟡 CVE-2025-31120: NamelessMC is a free, easy to ... ⚠️ CVE-2025-31118: NamelessMC is a free, easy to ... ⚠️ CVE-2025-30357: NamelessMC is a free, easy to ... ⚠️ CVE-2025-30158: NamelessMC is a free, easy to ... ⚠️ CVE-2025-29784: NamelessMC is a free, easy to ... 🟡 CVE-2025-27599: Element X Android is a Matrix ... 🟡 CVE-2025-3792: A vulnerability, which was cla... 🟡 CVE-2025-3791: A vulnerability classified as ... 🟡 CVE-2025-2950: IBM i 7.3, 7.4, 7.5, and 7.5 i... ⚠️ CVE-2025-29625: A buffer overflow vulnerabilit... 🟡 CVE-2025-3790: A vulnerability classified as ... 🟡 CVE-2025-3789: A vulnerability was found in b... 🟡 CVE-2025-32790: Dify is an open-source LLM app... 🟡 CVE-2024-46089: 74cms <=3.33 is vulnerable to ... 🟡 CVE-2024-49808: IBM Sterling Connect:Direct We... 🟡 CVE-2024-45651: IBM Sterling Connect:Direct We... 🟡 CVE-2025-3788: A vulnerability was found in b... 🟡 CVE-2025-3787: A vulnerability was found in P... 🟡 CVE-2025-3106: The LA-Studio Element Kit for ... ⚠️ CVE-2025-3786: A vulnerability was found in T... ⚠️ CVE-2025-3785: A vulnerability has been found... 🟡 CVE-2025-3056: The Download Manager plugin fo... 🔥 CVE-2025-2492: An improper authentication con... 🟡 CVE-2025-3783: A vulnerability classified as ... 🟡 CVE-2025-3598: The Coupon Affiliates – Affili... 🟡 CVE-2025-2162: The MapPress Maps for WordPres... 🔥 CVE-2025-1863: Insecure default settings have... 🔥 CVE-2025-39471: Improper Neutralization of Spe... ⚠️ CVE-2025-39470: Path Traversal: '.../...//' vu... ⚠️ CVE-2025-39469: Improper Neutralization of Inp... 🔥 CVE-2025-42599: Active! mail 6 BuildInfo: 6.60... ⚠️ CVE-2025-3520: The Avatar plugin for WordPres... 🟡 CVE-2025-2613: The Login Manager – Design Log... 🟡 CVE-2024-13650: The Piotnet Addons For Element... ⚠️ CVE-2025-25427: A Stored cross-site scripting ... ⚠️ CVE-2025-3509: A Remote Code Execution (RCE) ... ⚠️ CVE-2025-3246: An improper neutralization of ... 🟡 CVE-2025-3124: A missing authorization vulner... 🟢 CVE-2024-42178: HCL MyXalytics is affected by ... 🟡 CVE-2025-3765: A vulnerability, which was cla... 🟡 CVE-2025-3764: A vulnerability classified as ... 🟢 CVE-2024-42177: HCL MyXalytics is affected by ... 🟡 CVE-2025-3763: A vulnerability classified as ... 🟡 CVE-2025-3762: A vulnerability was found in P... 🟡 CVE-2025-29722: A CSRF vulnerability in Commer... 🟡 CVE-2025-28101: An arbitrary file deletion vul... 🔥 CVE-2025-28009: A SQL Injection vulnerability ... 🟢 CVE-2025-26269: DragonflyDB Dragonfly through ... 🟢 CVE-2025-26268: DragonflyDB Dragonfly before 1... ⚠️ CVE-2024-55211: An issue in Think Router Tk-Rt... 🟢 CVE-2021-47671: In the Linux kernel, the follo... ⚠️ CVE-2021-47670: In the Linux kernel, the follo... ⚠️ CVE-2021-47669: In the Linux kernel, the follo... ⚠️ CVE-2021-47668: In the Linux kernel, the follo... 🟢 CVE-2025-32415: In libxml2 before 2.13.8 and 2... ⚠️ CVE-2025-2947: IBM i 7.6  contains a privile... ⚠️ CVE-2025-29661: Litepubl CMS <= 7.0.9 is vulne... ⚠️ CVE-2025-29181: FOXCMS <= V1.25 is vulnerable ... ⚠️ CVE-2025-29180: In FOXCMS <=1.25, the installd... ⚠️ CVE-2025-29039: An issue in dlink DIR 832x 240... ⚠️ CVE-2025-43015: In JetBrains RubyMine before 2... 🟡 CVE-2025-43014: In JetBrains Toolbox App befor... 🟡 CVE-2025-43013: In JetBrains Toolbox App befor...
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