Cart Lift Abandoned Cart Recovery For Woocommerce And EddWordPress extension · Rextheme
CVE-2022-47449
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in RexTheme Cart Lift – Abandoned Cart Recovery for WooCommerce and EDD plugin <= 3.1.5 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 · high confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the RexTheme Cart Lift plugin for WooCommerce and Easy Digital Downloads. The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the HTTP response, potentially compromising user sessions or stealing credentials.
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
Cart Lift Abandoned Cart Recovery For Woocommerce And EddWordPress extension
<= 3.1.5CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check Cart Lift plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Cart Lift (Abandoned Cart Recovery For Woocommerce And Edd) and view the version number displayed beneath the plugin nameAffected if The displayed version is 3.1.5 or lower (any version <= 3.1.5)
-
Verify plugin is activeIn the WordPress plugins list, confirm the Cart Lift plugin status shows as 'Active'Affected if The plugin is active and the version is <= 3.1.5
-
Confirm plugin is publicly accessibleVisit the website frontend to verify the Cart Lift functionality is publicly reachable (no authentication required to trigger the affected endpoint)Affected if The plugin is live on a public-facing WooCommerce or Easy Digital Downloads site running version <= 3.1.5
A site is affected if it has the Cart Lift plugin installed, active, and running version 3.1.5 or lower, as this version contains the reflected XSS vulnerability in unsanitized user input.
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.
From vendor dataUpdate the Cart Lift plugin to version 3.1.6 or later. If immediate patching is not possible, implement Web Application Firewall (WAF) rules to block XSS attack patterns on the affected endpoint.
Fix this in Cart Lift Abandoned Cart Recovery For Woocommerce And Edd
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47449 — 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-47449 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