CVE-2026-78193

7.5High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.5High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: High impact on confidentiality
Weakness: CWE-89

Impact

Unauthenticated remote attackers can extract sensitive database contents via time-based SQL injection. They only need network access to hit the plugin's product.push endpoint.

Root cause

The identity linker fails to escape user input or use prepared statements before executing SQL queries during identity mapping.

Affected systems

JTL-Connector for WooCommerce (WordPress plugin) up to and including version 2.4.3

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Fix & remediation

Upgrade to a version higher than 2.4.3 once released. If patching cannot happen immediately, deactivate the JTL-Connector plugin or block access to the connector endpoint via your web server or WAF.

shell

$ wp plugin deactivate woo-jtl-connector

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

The JTL-Connector for WooCommerce plugin for WordPress is vulnerable to time-based SQL Injection via 'product.push' Identity Endpoint in all versions up to, and including, 2.4.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection fires during identity linking, before ProductController::push() executes, meaning exploitation succeeds even if downstream product handling would otherwise reject the request.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-78193