dbcve.org
Wpc Shop As A Customer For WoocommerceWordPress extension · Wpclever

CVE-2024-50416

HIGH · 8.8 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 1.2.7 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
Deserialization of Untrusted Data vulnerability in WPClever WPC Shop as a Customer for WooCommerce wpc-shop-as-customer allows Object Injection.This issue affects WPC Shop as a Customer for WooCommerce: from n/a through <= 1.2.6.

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

The WPClever WPC Shop as a Customer plugin for WooCommerce contains a deserialization vulnerability where untrusted data is being deserialized, allowing attackers to inject PHP objects. This Object Injection vulnerability can potentially lead to remote code execution if certain magic methods exist in the plugin or other installed plugins/themes.

MitigationUpdate WPC Shop as a Customer for WooCommerce to the latest version immediately. Until a patch is available, disable the plugin if possible and review the site for indicators of compromise.

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
Wpc Shop As A Customer For WoocommerceWordPress extension
Affected:< 1.2.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
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. Check if WPC Shop as a Customer plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Wpc Shop As A Customer For Woocommerce' or 'WPC Smart Manager' (the plugin may also be listed under related WPC bundles). Alternatively, check the /wp-content/plugins/ directory for folders containing 'wpc' and 'customer' in the name.
    Affected if Plugin is not found in the plugins list or directory
  2. Identify the installed version of the plugin
    In WordPress admin, go to Plugins > Installed Plugins > WPC Shop as a Customer and look for the version number displayed under the plugin name. If not visible in admin, check the main plugin PHP file header in /wp-content/plugins/ for the 'Version' tag.
    Affected if Version number cannot be determined or is not displayed
  3. Compare version against affected range
    Compare the installed version number to the affected range: any version below 1.2.7 is vulnerable. For example, 1.2.6, 1.2.5, 1.0.0 are all affected; 1.2.7 and above are not.
    Affected if Installed version is less than 1.2.7 (e.g., 1.2.6, 1.2.0, etc.)
  4. Verify deserialization entry points are accessible
    The vulnerability involves untrusted data deserialization. Review any frontend-facing forms, AJAX endpoints, or admin actions provided by this plugin that may accept serialized data. Check plugin settings for any import/functionality features that process data.
    Affected if Plugin features that handle serialized data are active and accessible to untrusted users

You are affected if the WPC Shop as a Customer plugin is installed and its version is below 1.2.7.

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.2.7 or later
Fixed in 1.2.7
Interim mitigation

Update WPC Shop as a Customer for WooCommerce to the latest version immediately. Until a patch is available, disable the plugin if possible and review the site for indicators of compromise.

Recommended fix High confidence

1.2.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WPC Shop as a Customer for WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.2.7 or later
  5. 5. Verify the update completed successfully
  6. 6. Test the plugin functionality to ensure the upgrade did not break any existing features

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

Fix this in Wpc Shop As A Customer For Woocommerce 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 the upgrade done

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