dbcve.org
Click Disable AllWordPress extension · Atakanau

CVE-2024-21749

HIGH · 8.8 CVSS v3.1 Published 2024-02-28
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Atakan Au 1 click disable all.This issue affects 1 click disable all: from n/a through 1.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the '1 click disable all' WordPress plugin (versions up to 1.0.1). Attackers can trick authenticated administrators into performing unintended actions (likely disabling all site functionality) by luring them to visit malicious pages that trigger forged requests.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions, validate these nonces on the server side, and set SameSite attribute on session cookies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Click Disable AllWordPress extension
Affected:<= 1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Atakanau Click Disable All'. Check the version number displayed under the plugin name.
    Affected if Plugin version is 1.0.1 or lower (the vulnerable version range is <= 1.0.1)
  2. Identify plugin admin interface
    Access the WordPress admin menu to find the plugin's settings page (typically under Settings or a custom menu item named after the plugin).
    Affected if Plugin is installed and activated, exposing its admin interface to authenticated administrators
  3. Inspect form actions for missing nonce fields
    View the source code of the plugin's admin page(s). Look for any HTML forms that perform state-changing actions (such as disabling site functionality). Check whether each form includes a nonce field (wp_nonce_field) for CSRF protection.
    Affected if Forms handling state-changing actions lack nonce token fields, indicating missing CSRF protection
  4. Check AJAX handlers for nonce verification
    Examine the plugin's PHP source code for AJAX action handlers (wp_ajax_* hooks). Verify whether each handler calls wp_verify_nonce or check_admin_referer before processing requests.
    Affected if AJAX handlers process requests without verifying nonce tokens, allowing forged requests to execute
  5. Review action processing logic
    Locate the plugin's main PHP file and any files handling the 'disable all' functionality. Trace the code path from form submission to action execution to identify whether any CSRF validation occurs.
    Affected if The plugin processes the 'disable all' action without validating request origin or authenticity

You are affected if the 'Atakanau Click Disable All' plugin (version 1.0.1 or lower) is installed and its forms or AJAX handlers lack nonce verification for state-changing actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions, validate these nonces on the server side, and set SameSite attribute on session cookies.

Fix this in Click Disable All Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21749 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data