Unauthenticated code execution via unrestricted file upload
Published Aug 10, 2026 · Updated Aug 10, 2026
Unrestricted file upload in Product Input Fields for WooCommerce 2.0.0 through 2.0.1 allows remote attackers to execute code. The file-field upload path treats an empty accepted-types setting as permission for every type and writes the submitted file beneath the web-accessible uploads tree. Guest checkout, a published product with that file field, and a server that executes files despite the upload directory rules are required for code execution.
Summary
What happened
Unrestricted file upload in Product Input Fields for WooCommerce 2.0.0 through 2.0.1 allows remote attackers to execute code. The file-field upload path treats an empty accepted-types setting as permission for every type and writes the submitted file beneath the web-accessible uploads tree. Guest checkout, a published product with that file field, and a server that executes files despite the upload directory rules are required for code execution.
The record
- CVE
- CVE-2026-19089
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- Tyche Softwares
- Product
- Product Input Fields for WooCommerce
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan proof of conceptfunctional · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo