Recover Abandoned Cart For WoocommerceWordPress extension · Sktthemes
CVE-2025-46243
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in sonalsinha21 Recover abandoned cart for WooCommerce recover-wc-abandoned-cart allows Cross Site Request Forgery.This issue affects Recover abandoned cart for WooCommerce: from n/a through <= 2.2.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Recover abandoned cart for WooCommerce plugin allows attackers to trick authenticated users into performing unintended actions (such as modifying cart recovery settings or manipulating abandoned cart data) by forcing their browser to send malicious requests.
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
Recover Abandoned Cart For WoocommerceWordPress extension
< 2.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedCheck if the 'Sktthemes Recover Abandoned Cart For Woocommerce' plugin exists in your WordPress plugins directory at wp-content/plugins/Affected if The plugin directory is present on the server
-
Check installed versionOpen the main plugin PHP file (typically in the plugin root directory) and locate the version in the plugin header comment, or view the plugin in WordPress admin under Plugins > Installed PluginsAffected if The version listed is below 2.3 (e.g., 2.2, 2.1, 2.0, etc.)
-
Identify state-changing admin actionsReview the plugin PHP files for admin action handlers (functions hooked to admin_post_, wp_ajax_, or admin_menu) that handle cart recovery settings or abandoned cart data modificationsAffected if The plugin has admin functions that process form submissions or URL parameters without checking WordPress nonces
-
Inspect nonce validation in vulnerable handlersSearch the plugin PHP files for wp_verify_nonce, check_admin_referer, or wp_create_nonce calls within functions that modify cart recovery settings or abandoned cart recordsAffected if The state-changing functions lack proper nonce verification or validation is missing entirely
You are affected if the plugin is installed and the version is below 2.3, especially if the admin-facing cart recovery functions do not validate nonces on requests that change settings or cart data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3
Update to a patched version when available. Until then, disable the plugin or implement additional request validation on the server side. Ensure WordPress nonces are properly implemented on all state-changing operations within the plugin.
2.3
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Recover Abandoned Cart For WooCommerce' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 2.3 from the WordPress plugin repository
- Verify the plugin is now running version 2.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Recover Abandoned Cart For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-46243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46243 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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