The Product Input Fields for WooCommerce WordPress plugin before 2.0.2 does not validate uploaded file types when its accepted-types setting is left empty, which its own documentation advertises as accepting all files, allowing unauthenticated attackers to upload arbitrary files and achieve remote code execution on servers that do not honour the directory's access rules.
Security readout for executives and security teams
Plain-English summary
A flaw in Product Input Fields for WooCommerce can let unauthenticated internet users upload arbitrary files when accepted file types are left blank. On servers where upload-directory access rules are not enforced, an attacker could run uploaded code and potentially take full control of the WordPress server, affecting confidentiality, integrity, and availability.
Executive priority
Treat affected public sites as an immediate remediation priority. The flaw crosses the network perimeter without credentials and may lead to server compromise. Prioritize identifying exposed installations, updating or disabling the plugin, checking upload-directory controls, and investigating for suspicious files or upload activity. Absence from KEV does not reduce the technical severity, but active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-19089 is a CWE-434 unrestricted file upload affecting plugin versions before 2.0.2. The vulnerable condition occurs when the accepted-types setting is empty, a configuration documented as accepting all files. Exploitation requires no authentication or user interaction. Remote code execution depends on the server failing to honour the upload directory's access restrictions.
Likely exposure
Highest risk applies to internet-accessible WooCommerce sites running a version before 2.0.2 with accepted-types left empty. Exposure to code execution additionally depends on web-server handling of uploaded files and enforcement of directory access rules. The supplied affected-version metadata specifically lists 2.0.0, while the vulnerability description covers all versions before 2.0.2.
Exploitation context
The CVSS 3.1 score is 9.8, reflecting network access, low complexity, no privileges, no user interaction, and potentially complete impact. The supplied bundle says this CVE is not in KEV and provides no evidence of active exploitation. A WPScan reference is tagged for exploit information, but the bundle does not establish public exploit availability or observed attacks.
Researcher notes
The core failure is missing file-type validation under the empty accepted-types configuration. Successful upload does not automatically prove code execution; researchers should separately validate whether the server executes uploaded content or disregards directory access rules. The bundle does not identify exact upload paths, affected server configurations, attack telemetry, or detailed patch changes, so those points remain unverified.
Mitigation direction
Update Product Input Fields for WooCommerce to version 2.0.2 or later.
Until updated, disable the plugin or remove unauthenticated file-upload functionality.
Configure explicit, restrictive accepted file types instead of leaving the setting empty.
Ensure upload directories cannot execute scripts and their access restrictions are enforced.
Review current vendor and WPScan guidance for any additional remediation details.
Validation and detection
Inventory all WordPress sites and confirm the installed plugin version.
Check whether accepted-types is empty on any product input field.
Verify uploaded files cannot be executed or served as active server-side content.
Review upload directories for unexpected executable or recently created files.
Examine web and application logs for suspicious unauthenticated upload activity.
After remediation, confirm the plugin reports version 2.0.2 or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.