Where
-Infinity
0

Vendor Risk Score

See how jtl-software compares to other vendors in security performance

View Risk Score →
Severity
8.6
XSS
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

The preview mode of the OPC (OnPage Composer) page builder of JTL-Shop is activated by a request parameter alone and renders page data supplied in the request without checking for an authenticated backend session with the corresponding permission. Several portlet properties are output without output encoding. An unauthenticated remote attacker can thereby cause script code to be executed in the browser of a visitor or administrator who opens a crafted link; in the case of an administrator, actions can be performed with the administrator's privileges. Third-party plugins whose portlets evaluate property values as templates can additionally be made to execute template code through the same entry point. This is a separate flaw in such plugins and does not affect the portlets of JTL-Shop itself.

First published (updated )
Severity
8.7
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The failed-login limiter of the JTL-Wawi synchronisation interface of JTL-Shop derives the client identity from the client-controlled X-Forwarded-For header and counts requests without credentials as failed logins. An unauthenticated remote attacker can block the synchronisation between JTL-Shop and JTL-Wawi with a few requests and repeat this indefinitely, so that orders are no longer handed over to JTL-Wawi. No data is disclosed and no code is executed.

First published (updated )
Severity
9.2
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

The web installer of JTL-Shop executes its state-changing installation tasks without checking whether the shop is already installed, and was not removed or locked after the installation. An unauthenticated remote attacker who can reach the installer directory can supply their own database credentials, create administrator and synchronisation accounts and overwrite the shop configuration. This can lead to a full takeover of the shop, including code execution on the server.

First published (updated )
Severity
8.8
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

The checkout of JTL-Shop stores the delivery address ID submitted by the customer in the session and adopts it into the order without verifying that the address belongs to the ordering customer. A remote attacker with access to the checkout, including a guest, can thereby attach the delivery address of another customer to their own order. Name and address of the other customer, and depending on the shop configuration further contact data, then appear in the order confirmation and customer account. As the IDs are sequential, addresses can be enumerated. Goods may also be shipped to the wrong address.

First published (updated )
Severity
8.7
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The authentication middleware of the JTL-Shop administration backend processes the plugin safe mode toggle on the admin logout route before checking whether the requesting user is authenticated. An unauthenticated remote attacker can therefore switch the shop's plugin safe mode on and off, which deactivates all installed plugins and their functionality, such as payment and shipping integrations, resulting in a shop-wide denial of service. The attack requires a single request and can be automated against many installations.

First published (updated )
Severity
7.5
SQL Injection
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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.

First published (updated )
Severity
9.3
AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

JTL Shop versions 5.2.0 through 5.7.1 contains a server-side template injection vulnerability that allows unauthenticated attackers to inject malicious template syntax due to unsanitized user-supplied input passed to the Smarty template engine. Attackers can exploit this flaw to read sensitive server-side values such as database credentials and encryption keys, and on versions 5.4.0 through 5.7.1, leverage registered Smarty modifiers including unserialize and filegetcontents to write a webshell to the web root and execute arbitrary commands as the web server user.

First published (updated )
Severity
7.5
SQL Injection
AV:N/AC:L/Au:N/C:P/I:P/A:P

SQL injection vulnerability in druckansicht.php in JTL-Shop 2 allows remote attackers to execute arbitrary SQL commands via the s parameter.

First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203