dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-39472

HIGH · 7.2 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Shop manager PHP Object Injection in WooCommerce PDF Invoices & Packing Slips < 5.9.0 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 confidence

PHP Object Injection vulnerability in WooCommerce PDF Invoices & Packing Slips plugin allows authenticated Shop Manager users to inject malicious PHP objects via unsanitized input, potentially leading to Remote Code Execution through magic methods in available classes.

MitigationUpgrade WooCommerce PDF Invoices & Packing Slips plugin to version 5.9.0 or later to patch the deserialization vulnerability. Restrict Shop Manager role permissions until update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

  1. Locate the WooCommerce PDF Invoices & Packing Slips plugin installation
    Check your WordPress wp-content/plugins/ directory for a folder named 'woocommerce-pdf-invoices-packing-slips' or similar. Within that folder, open the main plugin file (often plugin.php or index.php) to find the declared version number in the plugin header comment.
    Affected if The plugin is installed and the version displayed is lower than 5.9.0 (for example, 5.8.x, 5.7.x, etc.)
  2. Verify the installed version via WordPress admin
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'WooCommerce PDF Invoices & Packing Slips', and read the version number displayed beneath the plugin name.
    Affected if The version shown is anything before 5.9.0, indicating the vulnerable version is in use.
  3. Confirm WooCommerce is active
    In the WordPress admin under Plugins > Installed Plugins, verify that the WooCommerce plugin itself is active, as this plugin is a WooCommerce extension and the vulnerability requires WooCommerce to be present.
    Affected if WooCommerce is installed and active, providing the context in which the PDF Invoices plugin runs.
  4. Check for Shop Manager user accounts
    In WordPress admin, go to Users > All Users and review the list for any accounts assigned the Shop Manager role. The vulnerability specifically requires a user with Shop Manager (or higher) privileges.
    Affected if At least one user account with Shop Manager role exists in the system, creating the authenticated attack surface for this vulnerability.

You are affected if the WooCommerce PDF Invoices & Packing Slips plugin is installed at a version lower than 5.9.0 AND WooCommerce is active AND at least one Shop Manager user account exists in your WordPress installation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WooCommerce PDF Invoices & Packing Slips plugin to version 5.9.0 or later to patch the deserialization vulnerability. Restrict Shop Manager role permissions until update is applied.

Recommended fix Moderate confidence

5.9.0

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Locate WooCommerce PDF Invoices & Packing Slips plugin
  4. 4. If current version is below 5.9.0, click Update Now to upgrade to version 5.9.0 or later
  5. 5. Verify the update completed successfully by checking the plugin version
  6. 6. Test that PDF invoice generation works correctly on your store
  7. 7. Confirm that shop manager users can still access required functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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