dbcve.org
Wheel Of LifeWordPress extension · Kraftplugins

CVE-2024-3627

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to after 1.1.7 or later.
See remediation →
60/100
Remediation priority · Elevated
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 Wheel of Life: Coaching and Assessment Tool for Life Coach plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions in the AjaxFunctions.php file in all versions up to, and including, 1.1.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts and modify settings.

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 Wheel of Life WordPress plugin has a broken access control vulnerability in AjaxFunctions.php where multiple functions lack capability checks. Authenticated users with subscriber-level access can delete arbitrary posts and modify plugin settings without proper authorization.

MitigationUpdate the plugin to version 1.1.8 or later which includes proper capability checks. Until then, restrict subscriber-level account creation and monitor for suspicious post deletion or settings changes.

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.7

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
None
Integrity
Low
Availability
Low

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

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wheel of Life' by Kraftplugins. Alternatively, check the plugin directory /wp-content/plugins/wheel-of-life/ for the plugin files.
    Affected if The plugin is installed and the version is 1.1.7 or lower
  2. Determine installed version
    In WordPress admin_plugins list, the Wheel of Life plugin version is displayed under the plugin name. Alternatively, open /wp-content/plugins/wheel-of-life/readme.txt and check the 'Stable tag' or the version header in the main plugin PHP file.
    Affected if Version is 1.1.7 or lower (no version shown indicates an unupdated vulnerable version)
  3. Verify subscriber-level users exist
    In WordPress admin, go to Users and review the role assigned to each user. Look for any users with the Subscriber role.
    Affected if Any Subscriber-level accounts exist in the WordPress user database
  4. Check for unauthorized post deletions
    Review WordPress trash or deleted posts. Check site activity logs if available. Look for posts deleted by users who should not have deletion permissions for those posts.
    Affected if Posts were deleted by users without administrator-level access
  5. Inspect plugin settings for unauthorized changes
    Navigate to the Wheel of Life plugin settings page in WordPress admin and review current configuration. Compare against expected settings or check if settings were modified unexpectedly.
    Affected if Plugin settings have been changed without administrator action

User is affected if the Wheel of Life plugin version is 1.1.7 or lower AND subscriber-level user accounts exist in WordPress.

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.1.7
Interim mitigation

Update the plugin to version 1.1.8 or later which includes proper capability checks. Until then, restrict subscriber-level account creation and monitor for suspicious post deletion or settings changes.

Fix this in Wheel Of Life Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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