dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-39470

HIGH · 7.2 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Shop manager Privilege Escalation in WooCommerce Cart Abandonment Recovery < 2.1.0 versions.

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 privilege escalation vulnerability in the WooCommerce Cart Abandonment Recovery plugin (versions prior to 2.1.0) allows users with Shop Manager role to gain elevated administrative privileges, likely due to insufficient role-based access control (RBAC) checks within the plugin's admin functionality.

MitigationUpdate WooCommerce Cart Abandonment Recovery plugin to version 2.1.0 or later to patch the privilege escalation vulnerability.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 WooCommerce Cart Abandonment Recovery plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WooCommerce Cart Abandonment Recovery' or check the plugin files in wp-content/plugins/ for the cart-abandonment-recovery directory
    Affected if The plugin is present on the WordPress site
  2. Check the installed plugin version
    In WordPress admin Plugins page, click on the plugin to view details and note the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if Version is lower than 2.1.0 (e.g., 2.0.x, 1.x.x)
  3. Confirm Shop Manager role exists on the site
    In WordPress admin, go to Users > Roles or use a user role editor plugin to list all roles; look for 'Shop Manager' role which is added by WooCommerce
    Affected if The Shop Manager role is defined and present on the site
  4. Audit Shop Manager user accounts for unexpected admin privileges
    List all users with Shop Manager role via Users page, then manually inspect their user profile or use a role inspector to check if they have administrative capabilities (manage_options, update_core, etc.) they should not normally have
    Affected if Any Shop Manager user has been granted admin-level capabilities or elevated access they should not possess

You are affected if the WooCommerce Cart Abandonment Recovery plugin version is below 2.1.0 AND Shop Manager users exist on your site, as the insufficient RBAC checks could have allowed privilege escalation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WooCommerce Cart Abandonment Recovery plugin to version 2.1.0 or later to patch the privilege escalation vulnerability.

Recommended fix Moderate confidence

WooCommerce Cart Abandonment Recovery version 2.1.0 or later

  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 WooCommerce Cart Abandonment Recovery plugin
  4. Check the current installed version to confirm it is below 2.1.0
  5. If the plugin shows an update available, click 'Update Now' to update to version 2.1.0 or later
  6. If no update is available, manually download the latest version from the WordPress plugin repository or the plugin vendor
  7. Deactivate the current plugin, then delete the old version
  8. Upload and install the new version (2.1.0 or later)

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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