Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19089 – Unauthenticated Arbitrary File Upload leading to RCE – Product Input Fields for Woo

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19089 is a critical unrestricted file upload vulnerability (CWE-434) in the "Product Input Fields for WooCommerce" WordPress plugin. The plugin fails to validate uploaded file types when its "accepted-types" setting is left empty — a configuration the plugin’s own documentation states will accept all file types. This flaw allows unauthenticated attackers to upload arbitrary files, including executable scripts, and potentially achieve remote code execution on affected servers. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin’s file upload handler for product input fields does not enforce file extension/type restrictions when the administrator’s "accepted-types" setting is empty.
  • Trigger condition: Any WooCommerce store using the plugin with the accepted-types field left blank — a state the plugin documents as intentionally permitting all file types — is vulnerable.
  • Attack vector: Network-based; no authentication or user interaction is required. An attacker can submit a crafted file (e.g., a PHP script) through the exposed product input/upload field on the storefront.
  • Impact: Successful exploitation allows arbitrary file upload to the server. On servers that do not enforce restrictive execution permissions on the upload directory, this can lead to full remote code execution, resulting in complete loss of confidentiality, integrity, and availability.

Affected software

  • Product Input Fields for WooCommerce (WordPress plugin) — versions 2.0.0 to before 2.0.2

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Product Input Fields for WooCommerce to version 2.0.2 or later, which addresses the file type validation issue.
  • If immediate patching is not possible:
    • Explicitly configure the plugin’s "accepted-types" setting to a restrictive allow-list of safe, non-executable file extensions rather than leaving it empty.
    • Ensure the web server/hosting environment disables script execution (e.g., via .htaccess or Nginx location rules) in the WordPress uploads directory used by the plugin, to reduce the impact of any file upload bypass.
    • Monitor for unexpected file uploads or newly created files with executable extensions (.php, .phtml, etc.) in plugin upload paths.
    • Consider disabling the plugin’s upload feature entirely until patched if the risk cannot be otherwise mitigated.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge