dbcve.org
Woocommerce Pdf Invoices\, Packing Slips\, Delivery Notes And Shipping LabelsWordPress extension · Webtoffee

CVE-2024-3216

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-06
Fix available
A fix is available. Upgrade to 4.4.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wt_pklist_reset_settings() function in all versions up to, and including, 4.4.2. This makes it possible for unauthenticated attackers to reset all of the plugin's settings.

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 confidence

The WooCommerce PDF Invoices plugin has a broken access control vulnerability where the wt_pklist_reset_settings() function lacks a capability check, allowing unauthenticated attackers to reset all plugin settings to default via a simple HTTP request.

MitigationUpdate the plugin to version 4.4.3 or later which implements proper capability checks on the affected function.

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 Pdf Invoices\, Packing Slips\, Delivery Notes And Shipping LabelsWordPress extension
Affected:< 4.4.3

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Webtoffee Woocommerce PDF Invoices, Packing Slips, Delivery Notes And Shipping Labels' or 'WooCommerce PDF Invoices' by Webtoffee
    Affected if The plugin is not installed or has been removed entirely (not vulnerable)
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find the Webtoffee PDF Invoices plugin, and note the version number displayed below the plugin name
    Affected if The installed version is below 4.4.3 (for example, 4.4.2, 4.4.1, 4.4.0, or any earlier version)
  3. Confirm the vulnerable function exists (optional)
    Via FTP or file manager, locate the plugin directory (usually wp-content/plugins/wt-pklist-invoice) and search the PHP files for the string 'wt_pklist_reset_settings' to verify the function exists in the codebase
    Affected if The function exists without any capability check (nonce verification or current_user_can) before it processes the reset request

You are affected if the Webtoffee PDF Invoices plugin is installed and the version is below 4.4.3, as this version range lacks the capability check that prevents unauthenticated settings reset.

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 4.4.3 or later
Fixed in 4.4.3
Interim mitigation

Update the plugin to version 4.4.3 or later which implements proper capability checks on the affected function.

Recommended fix High confidence

4.4.3

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find 'WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels'
  4. Click 'Update now' to upgrade to version 4.4.3
  5. Alternatively, download version 4.4.3 from wordpress.org/plugins/woocommerce-pdf-invoices-packing-slips and upload via Plugins > Add New > Upload Plugin
  6. Verify the plugin version shows 4.4.3 after update
  7. Test that the plugin settings are accessible and functional

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

Fix this in Woocommerce Pdf Invoices\, Packing Slips\, Delivery Notes And Shipping Labels Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3216 — 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-2024-3216 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