Abandoned Cart RecoveryWordPress extension · Addify
CVE-2022-4888
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 · uneditedThe Checkout Fields Manager WordPress plugin before 1.0.2, Abandoned Cart Recovery WordPress plugin before 1.2.5, Custom Fields for WooCommerce WordPress plugin before 1.0.4, Custom Order Number WordPress plugin through 1.0.1, Custom Registration Forms Builder WordPress plugin before 1.0.2, Advanced Free Gifts WordPress plugin before 1.0.2, Gift Registry for WooCommerce WordPress plugin through 1.0.1, Image Watermark for WooCommerce WordPress plugin before 1.0.1, Order Approval for WooCommerce WordPress plugin before 1.1.0, Order Tracking for WooCommerce WordPress plugin before 1.0.2, Price Calculator for WooCommerce WordPress plugin through 1.0.3, Product Dynamic Pricing and Discounts WordPress plugin through 1.0.6, Product Labels and Stickers WordPress plugin through 1.0.1 have flawed CSRF checks in various places, which could allow attackers to make logged in users perform unwanted actions
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 analysisA detailed technical summary for this CVE is being prepared.
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
Abandoned Cart RecoveryWordPress extension
< 1.2.5
Advanced Free GiftsWordPress extension
< 1.0.2
Checkout Fields ManagerWordPress extension
< 1.0.2
Custom Fields For WoocommerceWordPress extension
< 1.0.4
Custom Order NumberWordPress extension
<= 1.0.1
Custom Registration Forms BuilderWordPress extension
< 1.0.2
Gift Registry For WoocommerceWordPress extension
<= 1.0.1
Image Watermark For WoocommerceWordPress extension
<= 1.0.1CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 · scoped1.0.21.0.41.2.5
Upgrade each plugin to: Abandoned Cart Recovery >= 1.2.5, Advanced Free Gifts >= 1.0.2, Checkout Fields Manager >= 1.0.2, Custom Fields For Woocommerce >= 1.0.4, Custom Order Number >= 1.0.2, Custom Registration Forms Builder >= 1.0.2, Gift Registry For Woocommerce >= 1.0.2, Image Watermark For Wooc
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. For each affected plugin (Abandoned Cart Recovery, Advanced Free Gifts, Checkout Fields Manager, Custom Fields For Woocommerce, Custom Order Number, Custom Registration Forms Builder, Gift Registry For Woocommerce, Image Watermark For Woocommerce), check the current version installed
- 4. Update each plugin to its fixed version: Abandoned Cart Recovery to 1.2.5 or later, Advanced Free Gifts to 1.0.2 or later, Checkout Fields Manager to 1.0.2 or later, Custom Fields For Woocommerce to 1.0.4 or later, Custom Order Number to 1.0.2 or later, Custom Registration Forms Builder to 1.0.2 or later, Gift Registry For Woocommerce to 1.0.2 or later, Image Watermark For Woocommerce to 1.0.2
- 5. Verify each plugin update was successful
- 6. Test that the plugins still function correctly after update
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4888 — 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-2022-4888 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