dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-2025

HIGH · 8.8 CVSS v3.1 Published 2024-03-23
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 "BuddyPress WooCommerce My Account Integration. Create WooCommerce Member Pages" plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.4.20 via deserialization of untrusted input in the get_simple_request function. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject a PHP Object. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. CVE-2024-32603 is likely a duplicate of this issue.

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 BuddyPress WooCommerce My Account Integration plugin for WordPress is vulnerable to PHP Object Injection via deserialization of untrusted input in the get_simple_request function. Authenticated attackers with subscriber-level access can inject PHP objects, and if a POP (Property Oriented Programming) chain exists through other plugins or themes, this can lead to arbitrary file deletion, data retrieval, or code execution.

MitigationUpdate the plugin to the latest version (3.4.21 or higher) and audit the WordPress installation for any evidence of POP chain exploitation via other plugins or themes.

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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BuddyPress WooCommerce My Account Integration' or check the wp-content/plugins directory for a folder containing 'bp-woocommerce-my-account' or similar naming
    Affected if The plugin appears in the list of installed plugins
  2. Determine the installed plugin version
    In WordPress admin Plugins list, click on the plugin name to view details, or inspect the main plugin PHP file header for 'Version:' comment, or check the plugin folder for a readme.txt/changelog containing version info
    Affected if The version number is lower than 3.4.21 or cannot be determined (assume vulnerable)
  3. Confirm subscriber-level access is possible
    Go to WordPress Settings > General > Membership and check if 'Anyone can register' is enabled, and what the 'New User Default Role' is set to (subscriber or higher-privileged role)
    Affected if User registration is enabled with subscriber or any role that could be exploited
  4. Inspect server logs for deserialization attempts
    Review Apache/nginx error logs and WordPress debug logs for unserialize() warnings, PHP warnings about object properties, or suspicious activity around the get_simple_request function endpoint
    Affected if Log entries show unserialize() calls on untrusted input or evidence of PHP object injection attempts
  5. Check for signs of exploitation via POP chain
    Look for unexpected files created or modified in wp-content/uploads, unexpected database entries, or suspicious PHP files; compare file hashes of core WordPress files and plugins against known good copies
    Affected if Unknown PHP files exist, file permissions have changed unexpectedly, or legitimate plugin/theme files show unauthorized modifications

Your environment is affected if the BuddyPress WooCommerce My Account Integration plugin is installed with a version lower than 3.4.21 and your site allows subscriber-level authenticated access.

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 plugin to the latest version (3.4.21 or higher) and audit the WordPress installation for any evidence of POP chain exploitation via other plugins or themes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,420
Get help mitigating

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-2025 — 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-2025 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