Side Cart WoocommerceWordPress extension · Xootix
CVE-2022-45376
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 XootiX Side Cart Woocommerce (Ajax) < 2.1 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the XootiX Side Cart WooCommerce (Ajax) plugin versions prior to 2.1 allows attackers to trick authenticated users into unknowingly submitting malicious requests due to missing or insufficient anti-CSRF token validation.
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
Side Cart WoocommerceWordPress extension
< 2.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
- 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.
-
Verify the XootiX Side Cart WooCommerce plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'XootiX Side Cart Woocommerce' or 'Side Cart Woocommerce (Ajax)' in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status
-
Determine the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins. Find the XootiX Side Cart plugin and locate the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/side-cart-woocommerce-ajax or similar) for the 'Version' header in the plugin comment block.Affected if The version number shown is less than 2.1 (for example: 2.0, 1.9, 1.8, etc.)
-
Confirm the plugin handles AJAX requestsInspect the plugin files for AJAX action hooks. Look in the main plugin file for calls to 'add_action' with 'wp_ajax' or 'wp_ajax_nopriv' prefixes, which indicate the plugin processes AJAX requests.Affected if The plugin contains AJAX action handlers that process requests without explicit CSRF token validation
A user is affected if the XootiX Side Cart WooCommerce plugin is installed with a version lower than 2.1 and the plugin is active on a WooCommerce site handling cart operations.
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.1
Update the XootiX Side Cart Woocommerce (Ajax) plugin to version 2.1 or later, which should include proper CSRF token validation for state-changing AJAX actions.
version 2.1 or later
- Backup your WordPress site and database before updating
- Navigate to WordPress Admin > Plugins > Installed Plugins
- Find 'Side Cart Woocommerce (Ajax)' by XootiX
- Click 'Update now' to upgrade to version 2.1 or later
- Verify the plugin version shows 2.1 or higher after update
- Test the side cart functionality (add/remove items) to confirm proper operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Side Cart Woocommerce
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45376 — 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-45376 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