dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-52704

CRITICAL · 10.0 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 →
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Edgar Rojas WooCommerce PDF Invoice Builder allows Remote Code Inclusion. This issue affects WooCommerce PDF Invoice Builder: from n/a through 2.0.8.

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

A code injection vulnerability in the WooCommerce PDF Invoice Builder plugin allows unauthenticated remote attackers to inject and execute malicious code, potentially achieving full remote code execution on the WordPress server and complete site compromise.

MitigationImmediately update to the latest version of the plugin (beyond 2.0.8) or disable the plugin until patched. Conduct a full forensic investigation to check for existing compromise, as CVSS 10 indicates likely active exploitation potential.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Verify WooCommerce PDF Invoice Builder plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WooCommerce PDF Invoice Builder' in the list
    Affected if plugin is present in the WordPress installation
  2. Check installed plugin version
    In the Plugins list, locate the WooCommerce PDF Invoice Builder plugin and note the version number displayed below the plugin name
    Affected if version is 2.0.8 or lower (versions 2.0.8 and below are affected)
  3. Confirm plugin is active
    In Plugins > Installed Plugins, verify the WooCommerce PDF Invoice Builder plugin shows as 'Active'
    Affected if plugin is active and accessible to unauthenticated users

If the WooCommerce PDF Invoice Builder plugin is installed, active, and running version 2.0.8 or lower, the environment is vulnerable to unauthenticated code injection and potential full site compromise.

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 to the latest version of the plugin (beyond 2.0.8) or disable the plugin until patched. Conduct a full forensic investigation to check for existing compromise, as CVSS 10 indicates likely active exploitation potential.

Recommended fix Moderate confidence

WooCommerce PDF Invoice Builder version 2.0.9 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WooCommerce PDF Invoice Builder' by Edgar Rojas
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 2.0.9 or higher
  6. 6. Test the invoice generation functionality to ensure the plugin works correctly after the update

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-2026-52704 — 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-52704 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