dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11643

HIGH · 8.8 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The Accessibility by AllAccessible plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'AllAccessible_save_settings' function in all versions up to, and including, 1.3.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 · high confidence

The AllAccessible WordPress plugin (versions up to 1.3.4) lacks a capability check on the 'AllAccessible_save_settings' function, allowing any authenticated user with Subscriber-level access or higher to modify arbitrary WordPress options. Attackers can change the default new user role to Administrator and enable user registration, then register an admin account and gain full site control.

MitigationUpdate the AllAccessible plugin to a version beyond 1.3.4 immediately. Until updated, temporarily disable user registration in WordPress settings and audit the site for unauthorized administrator accounts created since the plugin was installed.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify AllAccessible plugin version
    Go to WordPress admin dashboard > Plugins > Installed Plugins, locate AllAccessible and check the version number displayed. Compare it to the affected range (versions up to and including 1.3.4).
    Affected if The installed version is 1.3.4 or lower.
  2. Verify WordPress user registration is enabled
    Go to WordPress admin dashboard > Settings > General > Membership section, or inspect the 'users_can_register' option via database query: SELECT option_value FROM wp_options WHERE option_name = 'users_can_register';
    Affected if User registration is enabled (value is '1' or 'true').
  3. Check default new user role setting
    Go to WordPress admin dashboard > Settings > General > Default Role dropdown, or inspect the 'default_role' option via database query: SELECT option_value FROM wp_options WHERE option_name = 'default_role';
    Affected if The default role is set to 'administrator'.
  4. Audit for suspicious administrator accounts
    Query the wp_users and wp_usermeta tables: SELECT ID, user_login, user_email, user_registered FROM wp_users WHERE ID IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%'); Review registration dates against the timeline when AllAccessible was installed.
    Affected if There are administrator accounts created that were not intentionally created by legitimate site administrators.

A user is affected if the AllAccessible plugin version is 1.3.4 or lower AND user registration is enabled AND the default role is set to administrator, or if unauthorized administrator accounts exist on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the AllAccessible plugin to a version beyond 1.3.4 immediately. Until updated, temporarily disable user registration in WordPress settings and audit the site for unauthorized administrator accounts created since the plugin was installed.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11643 — 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-11643 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