Woocommerce Pdf Invoices\, Packing Slips\, Delivery Notes And Shipping LabelsWordPress extension · Webtoffee
CVE-2023-51546
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 · uneditedImproper Privilege Management vulnerability in WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels allows Privilege Escalation.This issue affects WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: from n/a through 4.2.1.
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 confidenceImproper Privilege Management vulnerability in the WebToffee WooCommerce PDF Invoices plugin allows authenticated users to escalate their privileges, likely due to missing or insufficient authorization checks on certain plugin functions that should be restricted to administrators.
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
< 4.3.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 plugin is installedCheck your WordPress wp-content/plugins directory for the 'wf-woocommerce-pdf-invoices' or 'wt-woocommerce-invoice' folder, or view the installed plugins in WP Admin > PluginsAffected if The plugin folder is present in the WordPress plugins directory
-
Identify the installed versionOpen the main plugin file (typically plugin.php or index.php inside the plugin folder) and locate the 'Version:' header in the plugin comment block, or check in WP Admin > Plugins > Installed PluginsAffected if The version number shown is less than 4.3.0 (such as 4.2.x, 4.1.x, or earlier)
-
Confirm non-administrator access existsReview WordPress user roles in WP Admin > Users and check if any users have roles other than Administrator (such as Editor, Author, Subscriber, or Shop Manager) who have access to the WordPress admin dashboardAffected if Any user with a role below Administrator has access to the WordPress admin area and can potentially trigger the vulnerable functions
Your environment is affected if the WebToffee WooCommerce PDF Invoices plugin is installed with a version below 4.3.0 and your site has non-administrator users who can access the WordPress admin dashboard.
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 · scoped4.3.0
Upgrade to a patched version of the plugin (4.2.2 or later). Until patched, restrict plugin access to administrator-level accounts only and monitor for unauthorized administrative account creation.
4.3.0
- Backup the WordPress site and database before performing any updates
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate 'WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels' by WebToffee
- Click 'Update Now' to update the plugin to version 4.3.0 or later
- Verify the update was successful by checking the installed plugin version
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
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51546 — 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-2023-51546 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