PDF Invoice for WooCommerce ≤ 7.1.1: A Checkout Note That Lands in unserialize() (CVE-2026-109220, CVSS 9.8)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

PDF Invoice for WooCommerce ≤ 7.1.1: A Checkout Note That Survives HTML, a PDF Library, and Lands in unserialize() (CVE-2026-109220, CVSS 9.8)

A customer note at checkout is supposed to be text — "please leave the parcel at the side door." In PDF Invoice for WooCommerce + Drag and Drop Template Builder, that note travels through invoice HTML, an HTML parser that decodes it back to life, and a PDF library — and arrives, unsanitized, at PHP's unserialize(). That is CVE-2026-109220, an unauthenticated PHP object injection to remote code execution scoring CVSS 9.8, and the CVE record names no patched version yet.

What Happened

CVE-2026-109220 is a PHP object injection vulnerability in the PDF Invoice for WooCommerce + Drag and Drop Template Builder plugin for WordPress, disclosed October 31, 2026 (CNA: Wordfence).

Am I Affected?

Check wp-admin → Plugins for PDF Invoice for WooCommerce + Drag and Drop Template Builder and its version. At 7.1.1 or below, you are in the affected range — and the exposed surface is any WooCommerce checkout that generates an invoice through this plugin.

One naming warning, because it matters here: this is not the similarly named free plugin "PDF Invoice for Woocommerce" (a different product, on its own version line). Do not transfer this CVE to that plugin — and do not reassure yourself with that plugin's version number if the Template Builder product is the one you run.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org listing or slug for this product, and the similarly named directory plugin is a different product, so keying a readme check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Disable the plugin — or at least its invoice generation — until the vendor ships a release naming this CVE. There is no patched version to update to yet; leaving the invoice path live leaves the customer_note path live.
  2. Audit the site as if someone may already have tried. Users → All Users: every Administrator should be a person you can name. Review recent orders for customer notes you cannot explain, and check recently modified and newly uploaded files for anything you do not recognize.
  3. Rotate what matters if anything looks off. Admin passwords and your WordPress salts are the cheap resets; do them before you need them, not after.
  4. When a fix does ship, update and confirm it names CVE-2026-109220. An update that does not mention this CVE is not evidence this CVE is fixed.

The Bigger Lesson

Data that crosses format boundaries gets re-interpreted at every boundary. The checkout note was "safe" as a database field, "safe" as escaped HTML, and then an HTML parser decoded it back into markup, a PDF library turned it back into bytes, and unserialize() treated those bytes as objects. Sanitizing for the first format is not sanitizing for the last one — every hand-off in a rendering pipeline is a new trust decision, and the dangerous code is the code that assumes someone upstream already made it.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running a WooCommerce store with PDF Invoice + Template Builder? Disable invoice generation until a patched release names this CVE, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report