dbcve.org
Wheel Of LifeWordPress extension · Kraftplugins

CVE-2024-47311

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.1.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Missing Authorization vulnerability in Kraft Plugins Wheel of Life wheel-of-life allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Wheel of Life: from n/a through <= 1.1.8.

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

Missing authorization vulnerability in the Wheel of Life WordPress plugin allows unauthenticated attackers to access functionality or data that should require proper access control validation. The plugin fails to enforce correct security level checks, enabling exploitation of incorrectly configured access controls.

MitigationImplement proper authorization checks across all sensitive functions and endpoints, enforce role-based access control (RBAC), and update to a patched version if available. Conduct access control audit to identify all vulnerable code paths.

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
Wheel Of LifeWordPress extension
Affected:< 1.1.9

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify the Wheel of Life plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wheel of Life' by Kraftplugins, or inspect the plugin files in wp-content/plugins/wheel-of-life/ for the main PHP file containing the version header
    Affected if The plugin is installed and active in the WordPress site
  2. Determine the installed version
    Check the plugin header in the main plugin file (wheel-of-life.php) for the 'Version' field, or view the plugin details in the WordPress plugins admin page
    Affected if The version is below 1.1.9 (any version from 1.0.0 through 1.1.8)
  3. Inspect AJAX handlers for missing capability checks
    Search plugin PHP files for add_action('wp_ajax_...) calls and verify each handler includes current_user_can() or similar authorization checks before executing sensitive operations
    Affected if AJAX endpoints exist without current_user_can() validation or authentication requirements
  4. Inspect REST API routes for missing authorization
    Search plugin PHP files for register_rest_route() calls and check if the permission_callback parameter is properly set to verify user capabilities
    Affected if REST API routes are registered without a permission_callback or with a weak/no authorization check
  5. Test unauthenticated access to admin functions
    Attempt to access known plugin admin pages or AJAX actions while logged out or as a low-privilege user (subscriber) to verify if requests are rejected
    Affected if Unauthenticated or low-privilege users can access administrative functionality without being blocked

A user is affected if the Wheel of Life plugin version is below 1.1.9 AND the plugin exposes AJAX endpoints, REST API routes, or admin pages that lack proper capability checks or authentication verification.

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.

dbcve · scoped
Upgrade available Upgrade to 1.1.9 or later
Fixed in 1.1.9
Interim mitigation

Implement proper authorization checks across all sensitive functions and endpoints, enforce role-based access control (RBAC), and update to a patched version if available. Conduct access control audit to identify all vulnerable code paths.

Recommended fix High confidence

1.1.9

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the 'Wheel Of Life' plugin.
  5. 5. If an update to version 1.1.9 is available, click 'Update Now' to install the fixed version.
  6. 6. Alternatively, download version 1.1.9 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 1.1.9 in the Plugins list.
  8. 8. Test the plugin functionality to ensure the update did not break any critical features.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wheel Of Life Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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