dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-13773

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Print Invoice & Delivery Notes for WooCommerce plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 5.8.0 via the 'WooCommerce_Delivery_Notes::update' function. This is due to missing capability check in the 'WooCommerce_Delivery_Notes::update' function, PHP enabled in Dompdf, and missing escape in the 'template.php' file. This makes it possible for unauthenticated attackers to execute code on the server.

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 Print Invoice & Delivery Notes for WooCommerce plugin before version 5.8.1 contains an unauthenticated Remote Code Execution vulnerability. The issue stems from three combined factors: missing capability/authorization checks in the WooCommerce_Delivery_Notes::update function allowing unauthenticated access, PHP execution being enabled in the Dompdf library which processes templates, and missing output escaping in template.php. This allows attackers to inject and execute arbitrary PHP code on the server via crafted requests.

MitigationImmediately update the plugin to version 5.8.1 or later which contains the security patch. As a temporary measure, consider disabling the plugin or deploying a WAF rule to block suspicious requests to the affected endpoints.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Print Invoice & Delivery Notes for WooCommerce' or check the plugins directory for the woocommerce-delivery-notes folder
    Affected if The plugin is present in the WordPress installation
  2. Check the installed version
    In WordPress admin plugins list, find the version number next to the plugin name, or open the main plugin file (usually woocommerce-delivery-notes/woocommerce-delivery-notes.php) and look for the Version header in the plugin comments
    Affected if The version is lower than 5.8.1 (e.g., 5.8.0, 5.7.x, etc.)
  3. Verify the vulnerable update function exists
    Check if the file includes/class-woocommerce-delivery-notes.php exists in the plugin directory and contains the 'update' function method within the WooCommerce_Delivery_Notes class
    Affected if The update function exists and lacks capability checks (the file contains 'function update()' without 'current_user_can' or similar authorization calls before the main logic)
  4. Confirm Dompdf library is present
    Check for the dompdf library folder in includes/lib/dompdf within the plugin directory
    Affected if The Dompdf library is bundled with the plugin and PHP execution is not disabled in its configuration

You are affected if the Print Invoice & Delivery Notes for WooCommerce plugin is installed with a version lower than 5.8.1 and the vulnerable update function with missing authorization checks is present in the codebase.

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

Immediately update the plugin to version 5.8.1 or later which contains the security patch. As a temporary measure, consider disabling the plugin or deploying a WAF rule to block suspicious requests to the affected endpoints.

Recommended fix High confidence

5.8.1 or later (latest stable release from WordPress plugin repository)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Print Invoice & Delivery Notes for WooCommerce' in the plugin list
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. After updating, verify the plugin is running version 5.8.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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