Skip to content
major vulnerability· requires attention

Unauthenticated RCE in a widely deployed WooCommerce plugin enabling full server compromise of e‑commerce WordPress sites.

Web

CVE-2026-103688

9.8
Critical
EPSS n/aPatch availableOct 29, 2026

Unauthenticated RCE via file upload in WooCommerce Checkout Files Upload plugin

common questions

Is CVE-2026-103688 being exploited?

Not confirmed. CVE-2026-103688 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-103688?

CVE-2026-103688 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-103688?

Yes. A fix has been recorded for CVE-2026-103688. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-103688 affect?

CVE-2026-103688 affects Checkout Files Upload for WooCommerce < 2.4.0, WordPress sites with the plugin installed, PHP web hosts executing files from uploads/. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-103688?

Update plugin to 2.4.0+, disable/limit uploads, and block PHP execution in uploads directory

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Checkout Files Upload for WooCommerce < 2.4.0WordPress sites with the plugin installedPHP web hosts executing files from uploads/
impact

Unauthenticated attackers can upload PHP/arbitrary files leading to remote code execution and full server compromise via the uploads directory.

action required

Immediate action required

affected versions
Unknown Checkout Files Upload for WooCommerce
  • affected< 2.4.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved