dbcve.org
Woocommerce Conversion TrackingWordPress extension · Wedevs

CVE-2023-52217

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 2.0.12 or later.
See remediation →
69/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
Missing Authorization vulnerability in weDevs WooCommerce Conversion Tracking.This issue affects WooCommerce Conversion Tracking: from n/a through 2.0.11.

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

A missing authorization vulnerability in the weDevs WooCommerce Conversion Tracking plugin (versions up to 2.0.11) allows unauthorized access to certain functionality or data due to improper or missing capability checks. This could permit unauthenticated or low-privilege users to perform actions intended only for administrators, potentially exposing conversion tracking data or allowing manipulation of tracking settings.

MitigationUpdate to version 2.0.12 or later which contains the authorization fix. If no update is available, consider removing the plugin until a patched version is released.

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
Woocommerce Conversion TrackingWordPress extension
Affected:< 2.0.12

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Confirm plugin installation
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'woocommerce-conversion-tracking' or similar. Check the plugin files for version information in the main plugin file header.
    Affected if Plugin is installed and version is below 2.0.12
  2. Verify installed version number
    Open the main plugin PHP file (usually named woocommerce-conversion-tracking.php or similar) and look for the 'Version:' header in the plugin comment block. Alternatively, check the WordPress plugins admin page for the installed version number.
    Affected if Version number is less than 2.0.12 (e.g., 2.0.11, 2.0.10, etc.)
  3. Identify user role configuration
    Navigate to WordPress admin > Users > Roles or use a user role editor plugin to list all defined user roles and their capabilities. Check for any roles with limited permissions that should not have admin access.
    Affected if Low-privilege roles (editor, author, contributor, subscriber, or custom roles) exist in the WordPress installation
  4. Inspect AJAX or admin-ajax.php endpoints
    Examine the plugin source code for AJAX action hooks (add_action calls with 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes) and admin action hooks. Check if these hooks verify user capabilities using functions like current_user_can() before performing administrative actions.
    Affected if Plugin contains AJAX or admin actions that do not perform capability checks (missing current_user_can() calls before sensitive operations)

Your environment is affected if the weDevs WooCommerce Conversion Tracking plugin is installed with any version prior to 2.0.12, as the missing authorization vulnerability exists in those versions regardless of user configuration.

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

Update to version 2.0.12 or later which contains the authorization fix. If no update is available, consider removing the plugin until a patched version is released.

Recommended fix Moderate confidence

2.0.12

  1. Create a complete backup of your WordPress site and database before updating
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate WooCommerce Conversion Tracking plugin
  4. Click Update Now or navigate to Plugins > Add New > Upload Plugin to upload version 2.0.12
  5. Verify the plugin updated successfully to version 2.0.12
  6. Test WooCommerce order tracking and conversion functionality to ensure the update did not break existing features
  7. Clear any caching plugins or server-side caches after the update

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

Fix this in Woocommerce Conversion Tracking Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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