Skip to content
Web

CVE-2026-19089

9.8
Critical
EPSS 0.46%Patch availableAug 13, 2026

Unauthenticated file-upload flaw in WooCommerce plugin allows remote code execution.

common questions

Is CVE-2026-19089 being exploited?

Not confirmed. CVE-2026-19089 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-19089?

CVE-2026-19089 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19089?

Yes. A fix has been recorded for CVE-2026-19089. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19089 affect?

CVE-2026-19089 affects Product Input Fields for WooCommerce (plugin) < 2.0.2, WordPress sites running WooCommerce, PHP web servers that execute uploaded files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19089?

Update plugin to 2.0.2+ and ensure upload directories disallow code execution

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Product Input Fields for WooCommerce (plugin) < 2.0.2WordPress sites running WooCommercePHP web servers that execute uploaded files
impact

Unauthenticated attackers can upload arbitrary files and achieve remote code execution if the server executes files in upload directories.

action required

Immediate action required

affected versions
Unknown Product Input Fields for WooCommerce
  • affected>= 2.0.0 and < 2.0.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free