dbcve.org
Canada Post Shipping MethodWordPress extension · Automattic

CVE-2023-47789

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 2.8.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in WooCommerce Canada Post Shipping Method.This issue affects Canada Post Shipping Method: from n/a through 2.8.3.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Canada Post Shipping Method plugin allows attackers to trick authenticated administrators into performing unintended state-changing actions (e.g., modifying shipping settings, rates, or configuration) by exploiting the lack of anti-CSRF tokens on sensitive form submissions and AJAX endpoints.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations in the plugin, validate the request origin/referer header, and set SameSite attribute on session cookies.

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
Canada Post Shipping MethodWordPress extension
Affected:< 2.8.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Canada Post Shipping plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Canada Post Shipping Method' or check the plugins directory for the Canada Post shipping plugin files
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the Canada Post Shipping Method plugin to view its version, or inspect the main plugin file header for the 'Version' field
    Affected if Version is less than 2.8.4 or version information cannot be determined (indicating an old or unmaintained installation)
  3. Confirm administrative access exists
    Check if you have administrator-level access to the WordPress site where the plugin is installed; CSRF attacks require an authenticated administrator to trigger the malicious request
    Affected if Administrator WordPress credentials are available for this site
  4. Inspect plugin for nonce implementation
    Examine the plugin PHP files (especially form handlers and AJAX endpoints) for the presence of wp_verify_nonce or check_admin_referer calls when processing state-changing requests
    Affected if State-changing operations (shipping settings, rates, configuration) lack nonce verification code

A WordPress site is affected if it has the Canada Post Shipping Method plugin installed with version less than 2.8.4 and uses administrative functionality to modify shipping settings without CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8.4 or later
Fixed in 2.8.4
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations in the plugin, validate the request origin/referer header, and set SameSite attribute on session cookies.

Recommended fix High confidence

2.8.4

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Find the Canada Post Shipping Method plugin
  4. Click Update Now if an update to version 2.8.4 or later is available, or manually upload version 2.8.4 from the WordPress plugin repository
  5. Verify the plugin update was successful by checking the installed version number
  6. Test that the WooCommerce shipping functionality continues to work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Canada Post Shipping Method Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47789 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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