dbcve.org
Buddypress Woocommerce My Account Integration. Create Woocommerce Member PagesWordPress extension · Themekraft

CVE-2024-35726

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 3.4.20 or later.
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
Missing Authorization vulnerability in ThemeKraft WooBuddy.This issue affects WooBuddy: from n/a through 3.4.19.

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 ThemeKraft WooBuddy plugin up to version 3.4.19 allows unauthenticated or unauthorized users to access functionality they should not have permission to use, likely due to missing capability checks or nonce validation on sensitive operations.

MitigationUpdate to the latest version of WooBuddy if a patch is available, or disable the plugin until a fix can be applied. If update unavailable, restrict access to the plugin's admin pages via server-level access controls.

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
Buddypress Woocommerce My Account Integration. Create Woocommerce Member PagesWordPress extension
Affected:< 3.4.20

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. Locate the plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Themekraft Buddypress Woocommerce My Account Integration' or 'WooBuddy'. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually in wp-content/plugins/woobuddy-woo-buddy/ or similar path) and look for the 'Version' header in the plugin comment block.
    Affected if Version number displayed is less than 3.4.20 (e.g., 3.4.19, 3.4.18, etc.)
  2. Verify the exact version string
    Access the plugin file directly via file manager or FTP. Common paths include wp-content/plugins/woobuddy-woo-buddy/woobuddy.php or wp-content/plugins/bp-woocommerce-member-pages/loader.php. Open the main PHP file and locate the 'Version:' field in the plugin header comment.
    Affected if The Version field shows any version before 3.4.20, such as 3.4.19, 3.4.0, or earlier releases.
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the Themekraft/WooBuddy plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and the version is below 3.4.20.

You are affected if the Themekraft Buddypress Woocommerce My Account Integration plugin is installed, active, and running any version lower than 3.4.20, as this version range lacks proper capability checks or nonce validation on sensitive operations.

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 3.4.20 or later
Fixed in 3.4.20
Interim mitigation

Update to the latest version of WooBuddy if a patch is available, or disable the plugin until a fix can be applied. If update unavailable, restrict access to the plugin's admin pages via server-level access controls.

Recommended fix Moderate confidence

3.4.20

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the 'Create Woocommerce Member Pages' (WooBuddy) plugin by ThemeKraft
  4. Update the plugin to version 3.4.20 or later
  5. Verify the update was successful by checking the installed plugin version
  6. Test the WooCommerce member pages functionality to ensure the integration works correctly after the update

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

Fix this in Buddypress Woocommerce My Account Integration. Create Woocommerce Member Pages Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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