Skip to content
Laskyr

CVE-2026-109220: PDF Invoice for WooCommerce + Drag and Drop Te… PHP object injection vulnerability

critical 9.8 published 2026-10-31 · updated 2026-11-03

Fixed in PDF Invoice for WooCommerce + Drag and Drop Te… 7.2.0 (first release after the affected range)

PDF Invoice for WooCommerce + Drag and Drop Te… 7.1.1 and older is affected by this PHP object injection issue. Sites on 7.2.0 or newer are not affected; the latest release is 7.2.0.

Affected versions
7.1.1 and older
Fixed in
7.2.0 *
Latest version
7.2.0
Severity
Critical · CVSS 9.8
Active installs
500+
Type
PHP object injection

* The source does not name a fixed version; this is the first wordpress.org release after the last affected version.

What an attacker needs

CVSS vector (score by Wordfence): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do now

  1. Update PDF Invoice for WooCommerce + Drag and Drop Te… to 7.2.0 or newer: Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. Not sure which version you run? Check your version against every known PDF Invoice for WooCommerce + Drag and Drop Te… issue. With WP-CLI: wp plugin get pdf-for-woocommerce --field=version.
  5. If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

The advisory

The PDF Invoice for WooCommerce + Drag and Drop Template Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.1.1 via the 'customer_note' parameter parameter. This is due to insufficient sanitization of the customer_note checkout field, which is inlined verbatim into invoice HTML, entity-decoded back into a live tag by simplehtmldom, reassembled into raw bytes by mPDF, and passed to unserialize() in _getObjAttr without validation. This makes it possible for unauthenticated attackers to execute code on the server. An unauthenticated attacker can trigger the vulnerable code path on a default install by placing an anonymous WooCommerce checkout via the public Store API (POST /wc/store/v1/checkout) using a Direct Bank Transfer or cheque payment method, which automatically transitions the order to 'on-hold' status and fires the plugin's invoice-generation hook.

Description from the CVE record, published by Wordfence (the CVE Numbering Authority), via the NVD entry for CVE-2026-109220.

References

Related

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit