Loading vulnerability…
CVE-2026-19089 is an arbitrary file upload vulnerability in the Product Input Fields for WooCommerce WordPress plugin before version 2.0.2. When the plugin's accepted-types upload setting is left empty, uploaded file types are not validated, despite the configuration being documented as allowing all file types. This allows unauthenticated attackers to submit arbitrary files through affected product input upload functionality. In environments where the server permits execution of uploaded content or does not properly enforce non-executable access rules on the upload directory, the flaw can be leveraged to achieve remote code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
The repository contains a single Python 3 draft exploit and a README. The script accepts a target base URL, a product URL, and an optional shell filename; it uses requests with a browser-like User-Agent, drives an unauthenticated WooCommerce guest/COD order flow, and attempts to persist an uploaded attacker-provided PHP webshell through a Product Input Fields (PIF) field. After checkout, it follows a returned order redirect and scrapes it for product_input_fields upload URLs. If that fails, it brute-forces numeric upload prefixes from 1 through 499 under the predictable WordPress uploads path. It tests candidate files by POSTing x=echo SHELL_OK; and reports a live endpoint only when that marker is returned. No PHP webshell is present, so this is best classified as a proof-of-concept automation draft rather than a complete standalone RCE exploit. The README explicitly describes the repository as incomplete/work in progress and notes inconsistent or pending version-and-patch mapping. The code's stated affected-version ranges are also internally inconsistent: the header lists 1.0.0-1.1.12 and 2.0.1-2.0.2, while the banner lists 2.0.0-2.0.1.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.