dbcve.org
CWE-497Weakness · CWE-497

CVE-2026-56060

HIGH · 7.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Sensitive Data Exposure in Print Invoice & Delivery Notes for WooCommerce <= 7.1.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 confidence

The Print Invoice & Delivery Notes plugin for WooCommerce exposes sensitive data (likely order invoices or customer information) through an unprotected endpoint that can be accessed without authentication. An unauthenticated attacker can directly access the vulnerable URL/path to retrieve sensitive information.

MitigationUpdate the Print Invoice & Delivery Notes plugin to the latest patched version immediately. Until patched, restrict access to the vulnerable endpoint via web server configuration or disable the plugin if no update is available.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm the Print Invoice & Delivery Notes plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Print Invoice & Delivery Notes for WooCommerce' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin in the WordPress plugins list or check the plugin header in /wp-content/plugins/woocommerce-delivery-notes/woocommerce-delivery-notes.php for the 'Version' defined constant
    Affected if The version number cannot be verified or is older than the current patched version available from the vendor
  3. Identify the vulnerable endpoint URL
    Review the plugin settings page under WooCommerce > Settings > Print Invoice & Delivery Notes; the endpoint typically follows patterns like /?wc-api=print_invoice or /?action=print_invoice&order_id= in the plugin
    Affected if An endpoint URL is accessible that handles invoice or delivery note generation
  4. Test unauthenticated access to the endpoint
    Open the identified endpoint URL in a browser or curl command from an incognito window (not logged into WordPress)
    Affected if The endpoint returns order invoices, delivery notes, or customer PII without requiring WordPress or WooCommerce login
  5. Verify if sensitive data is exposed
    Examine the response from the unauthenticated endpoint request - check for customer names, addresses, order details, payment information, or invoice contents
    Affected if Sensitive order or customer data is displayed in the response without authentication

If the plugin is installed and the endpoint is accessible without authentication while returning sensitive order or customer data, the environment is affected by this CVE.

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

Update the Print Invoice & Delivery Notes plugin to the latest patched version immediately. Until patched, restrict access to the vulnerable endpoint via web server configuration or disable the plugin if no update is available.

Recommended fix Moderate confidence

Latest version available from vendor (7.1.2 or higher)

  1. Update the Print Invoice & Delivery Notes for WooCommerce plugin to the latest version available from the WordPress plugin repository or the vendor.
  2. After updating, verify the sensitive data exposure vulnerability is resolved by testing invoice/delivery note access controls.
  3. Ensure the updated plugin version is 7.1.2 or later.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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