CyberSecBulletin
CVE-2026-87855NVD status: Deferred

JTL-Connector for WooCommerce: Unrestricted Upload of File with Dangerous Type

CVE-2026-87855 is a critical-severity unrestricted upload of file with dangerous type vulnerability in JTL-Connector for WooCommerce from Ntbyk, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected JTL-Connector for WooCommerce versions: 2.4.3 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.79% chance of exploitation within 30 days, higher than 57% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of JTL-Connector for WooCommerce you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
NtbykJTL-Connector for WooCommerce2.4.3 and earlierNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (wordfence.com).

Official description

The JTL-Connector for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.4.3 via the saveImage() function. This is due to the startSession() function accepting an empty jtlauth parameter as a valid credential, combined with insufficient file type validation in handleImagePush(). This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Unrestricted Upload of File with Dangerous Type

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

How developers prevent this class of flaw

  • Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
  • When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
  • Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.

More Unrestricted Upload of File with Dangerous Type vulnerabilities (CWE-434)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).

References

Other vulnerabilities in JTL-Connector for WooCommerce

All JTL-Connector for WooCommerce vulnerabilities

Recent Unrestricted Upload of File with Dangerous Type vulnerabilities

Spotted an error? Tell us.