Security readout for executives and security teams
Plain-English summary
A WordPress plugin called “1 click disable all” has a CSRF flaw through version 1.0.1. If a site user with relevant permissions is tricked into an action, plugin behavior could be changed without an intended request. The public evidence rates this medium, not emergency-level.
Executive priority
Treat as a routine but real WordPress maintenance risk. Prioritize internet-facing or business-critical sites first, especially where administrators manage plugins frequently. It does not justify crisis response based on the supplied evidence.
Technical view
CVE-2024-21749 is CWE-352 CSRF affecting Atakan Au “1 click disable all” through 1.0.1. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, with low integrity and availability impact. Sources do not specify endpoint details, required victim role, or fixed version.
Likely exposure
Exposure is limited to WordPress installations using the Atakan Au “1 click disable all” plugin through version 1.0.1. The bundle also references packageName “first-graders-toolbox,” so confirm plugin identity during inventory.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires user interaction and likely depends on the victim’s WordPress privileges, but the public bundle does not define the exact role or workflow.
Researcher notes
Public detail is sparse. The record identifies CSRF, CVSS vector, affected plugin through 1.0.1, and Patchstack as the vulnerability database source. It does not provide proof-of-concept details, endpoint names, nonce behavior, required role, fixed release, or exploitation telemetry.
Mitigation direction
- Inventory WordPress sites for the named plugin and version through 1.0.1.
- Check vendor or Patchstack guidance for a fixed version or official mitigation.
- Disable or remove the plugin where it is not business-critical.
- Restrict administrative access and reinforce anti-phishing controls for WordPress users.
- Monitor WordPress logs for unexpected plugin setting or availability changes.
Validation and detection
- Confirm whether the plugin is installed on any WordPress site.
- Record installed plugin version and compare against affected range through 1.0.1.
- Review available vendor or Patchstack advisory details for remediation status.
- Check whether recent plugin configuration changes were authorized.
- Verify compensating controls around WordPress admin sessions and user training.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-21749 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
