dbcve.org
CodesignerWordPress extension · Codexpert

CVE-2024-4371

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 4.5 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
The CoDesigner WooCommerce Builder for Elementor – Customize Checkout, Shop, Email, Products & More plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.4.1 via deserialization of untrusted input from the recently_viewed_products cookie. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable plugin. 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.

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 CoDesigner plugin deserializes untrusted data from the recently_viewed_products cookie without sanitization, enabling unauthenticated PHP Object Injection. While the plugin lacks a native POP chain, attackers can leverage POP chains from other plugins/themes present on the WordPress installation to achieve arbitrary file deletion, data theft, or remote code execution.

MitigationUpdate to version 4.4.2 or later immediately. If unable to patch quickly, disable the plugin and consider removing the recently_viewed_products cookie handling at the web server level as a temporary measure.

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
CodesignerWordPress extension
Affected:< 4.5

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. Confirm CoDesigner plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check /wp-content/plugins/ directory for a folder named 'codesigner' or 'co-designer'. Use WP-CLI: wp plugin list --name='codesigner' --format=json
    Affected if Plugin is not found in the WordPress installation
  2. Identify installed CoDesigner version
    In WordPress admin, go to Plugins > Installed Plugins and locate CoDesigner to view the version number. Alternatively, inspect the main plugin file (usually codesigner.php) and look for the 'Version' header in the plugin comments, or check the plugin's readme.txt file
    Affected if Version number is less than 4.5 (vulnerable) or cannot be determined (treat as vulnerable)
  3. Check if recently_viewed_products cookie is being processed
    Use browser developer tools (Application > Cookies) to inspect if the recently_viewed_products cookie exists. Review plugin source code in includes/class-settings.php or similar files for unserialize() calls on $_COOKIE['recently_viewed_products']. Use grep: grep -r 'recently_viewed_products' /path/to/wp-content/plugins/codesigner/
    Affected if The cookie exists and the plugin code contains unserialize() calls on cookie data without prior sanitization

A WordPress site is affected if the CoDesigner plugin is installed with a version below 4.5 and the recently_viewed_products cookie is present and processed by the vulnerable deserialization code path.

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

Update to version 4.4.2 or later immediately. If unable to patch quickly, disable the plugin and consider removing the recently_viewed_products cookie handling at the web server level as a temporary measure.

Recommended fix High confidence

4.5

  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. Find the CoDesigner (formerly WooCommerce Builder for Elementor) plugin
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.5 or later
  6. 6. Alternatively, download version 4.5 or later from the WordPress plugin repository and upload it manually
  7. 7. Verify the plugin version after updating to confirm the upgrade was successful
  8. 8. Clear any existing 'recently_viewed_products' cookies on the site as a precautionary measure

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

Fix this in Codesigner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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