Skip to main content
VulnerabilityPublished

CVE-2026-123122: Checkout Files Upload for WooCommerce (WordPress plugin) · Cross-site Scripting

Affects Checkout Files Upload for WooCommerce (WordPress plugin)Source CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited : upgrade to 2.4.1 soon.

Data as of 14 Nov 2026, 06:17 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.4.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Checkout Files Upload for WooCommerce (WordPress plugin) to 2.4.1.

Affected software

ProductAffectedFixed in
Checkout Files Upload for WooCommerceAffected
  • >=2.4.0 <2.4.1
Fixed in
  • 2.4.1

AI-suggested

Upgrade the Checkout Files Upload for WooCommerce plugin to version 2.4.1 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

A cross-site scripting (XSS) vulnerability exists in the Checkout Files Upload for WooCommerce WordPress plugin versions 2.4.0 up to but not including 2.4.1. The plugin fails to properly verify uploaded file types at checkout, allowing unauthenticated users to upload HTML files disguised as images. When a shop manager or administrator views the uploaded file from the order screen, the malicious JavaScript executes in their browser. This issue is a regression of a previously fixed vulnerability (CVE-2025-4212) and was reintroduced in version 2.4.0.

References

Community reviews

Loading reviews…