CVE-2026-123122 · Package
NO FIX YET · SEE WHAT TO DO
The Checkout Files Upload for WooCommerce WordPress plugin before 2.4.1 accepts HTML files disguised as images at checkout and serves them inline. An unauthenticated visitor can plant JavaScript that runs in the browser of a shop manager or administrator who opens the file from the order screen.
first public Nov 14, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Stores running the Checkout Files Upload for WooCommerce WordPress plugin before 2.4.1, including 2.4.0. The risk arises because anyone can upload at checkout and staff open the files from the order screen. Sites without this plugin, or running 2.4.1 or later, are not affected.
Not affected if plugin-not-installed, version-2.4.1-or-later
Who cares checkout-files-upload, woocommerce, wordpress
2.4.1, and the sources say 2.4.0 reintroduced the flaw.2.4.1 or later.The Checkout Files Upload for WooCommerce WordPress plugin before 2.4.1 does not verify that a file uploaded at checkout is really one of its allowed image types, and serves stored uploads inline using their detected content type, allowing unauthenticated users to upload an HTML file disguised as an image that executes JavaScript in the browser of a shop manager or administrator who opens it from the order screen. This is a regression of CVE-2025-4212, reintroduced in 2.4.0.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.