Woocommerce Weight Based ShippingWordPress extension · Weightbasedshipping
CVE-2022-46794
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 weightbasedshipping.Com WooCommerce Weight Based Shipping plugin <= 5.4.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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Weight Based Shipping plugin allows attackers to forge requests on behalf of authenticated administrators due to missing or inadequate anti-CSRF token validation. Successful exploitation could enable unauthorized modification of shipping settings or other privileged actions.
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
Woocommerce Weight Based ShippingWordPress extension
<= 5.4.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 plugin installation and versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'WooCommerce Weight Based Shipping' (or 'Weightbasedshipping'), and record the version number displayed. Alternatively, use WP-CLI: wp plugin list --name='weightbasedshipping' --format=jsonAffected if Version is 5.4.1 or lower (or version field is empty/unavailable indicating very old install)
-
Confirm WooCommerce is activeIn WordPress admin, verify WooCommerce plugin status is Active. CSRF impact requires WooCommerce to be functional since shipping settings are part of WooCommerce commerce flowsAffected if WooCommerce is active and Weight Based Shipping plugin is enabled
-
Identify admin-accessible plugin pagesIn WordPress admin, navigate to WooCommerce > Shipping > Weight Based Shipping (or similar menu item under WooCommerce). Note the URL and form actions present on these settings pagesAffected if Plugin settings pages exist and contain forms that modify shipping configuration
-
Inspect plugin code for nonce validationAccess the plugin directory via file manager or FTP (typically wp-content/plugins/weightbasedshipping/). Open PHP files that handle form submissions (look for save, update, or settings-related files). Search for occurrences of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' functionsAffected if No nonce verification functions are found in files handling form submissions, OR code contains form submissions without these validations
-
Check for AJAX actions without nonce checksIn plugin PHP files, locate any add_action('wp_ajax_*) hooks. Verify if these AJAX handlers include nonce validation before processing requestsAffected if AJAX endpoints exist that process admin actions without nonce verification
User is affected if the Weight Based Shipping plugin version is 5.4.1 or lower, WooCommerce is active, and the plugin handles admin form submissions without proper CSRF token validation in the code.
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 plugin to a version beyond 5.4.1. Alternatively, implement WordPress nonce verification on all form submissions and admin actions within the plugin.
Fix this in Woocommerce Weight Based Shipping
Scoped from the published advisory
- Consultation1.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46794 — 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-46794 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