CVE-2026-19089 json
Product Input Fields for WooCommerce < 2.0.2 - Unauthenticated Arbitrary File Upload
published 2mo ago modified 2mo ago also EUVD-2026-55001
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- Unknown Product Input Fields for WooCommerce 2.0.2
Is CVE-2026-19089 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
3.23% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Product Input Fields for WooCommerce < 2.0.2 - Arbitrary File Upload to RCE nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/c5728a31-de92-40df-ab19-aec4db84ba21/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown Product Input Fields for WooCommerce
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
-
wpscan.com
/vulnerability/c5728a31-de92-40df-ab19-aec4db84ba21/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-19089
- NVD CVE-2026-19089
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.