Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed JTL-Shop admin route
-
DeliverySend unauthenticated request to logout route
-
ExploitToggle plugin safe mode pre-auth
-
ExecutionDeactivate all plugins including payment/shipping
-
ImpactShop-wide denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of JTL-Shop, because the admin logout route processes the plugin safe mode toggle in the authentication middleware before checking whether the requester is authenticated (CWE-306). The only prerequisite is network reachability of the shop's administration backend; the attack needs a single request, no credentials, and no user interaction. Limiting factors: impact is confined to availability (toggling plugin safe mode disables plugins) with no data exposure or code execution, and exposure can be reduced where the admin backend is network-restricted (e.g., IP-allowlisted or behind a VPN) rather than internet-facing. |
| Impact | This is a genuine high-priority availability issue despite impacting only availability. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms a remote, unauthenticated, low-complexity attack with no user interaction, and CWE-306 (Missing Authentication for a Critical Function) is consistent with the described flaw: the authentication middleware processes the plugin safe mode toggle on the admin logout route before verifying authentication. The 8.7 base score is driven entirely by VA:H (high availability impact) with no confidentiality or integrity impact, which is accurate - an attacker cannot read data or execute code, only disable all plugins (payment, shipping, etc.) to cause a shop-wide DoS. Weighing the signals: the attack surface and triviality are serious (single automatable request against many installations per the description), but no EPSS score, no CISA KEV listing, and no POC were provided in the input, so there is no evidence of active exploitation or public exploit code yet. Net assessment: a real, easily-weaponizable DoS primitive that merits prompt patching, but current exploitation-in-the-wild evidence is absent from the available data - treat as high urgency on exposure/ease grounds rather than on confirmed active abuse. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a single crafted request to the JTL-Shop admin logout route, which processes the plugin safe mode toggle before any authentication check, flipping the shop into safe mode. This deactivates all installed plugins - including payment and shipping integrations - rendering the storefront unable to complete transactions and causing a shop-wide denial of service. Because the request requires no credentials and no user interaction, it can be scripted and fired at many installations at once; no public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated remote attackers can disable every installed plugin on JTL-Shop installations - including payment and shipping integrations - by toggling the plugin safe mode through the administration backend's logout route, which is processed before the request's authentication state is checked (CWE-306). The attack needs a single request, no credentials and no user interaction, and can be automated across many installations to produce a shop-wide denial of service; CVSS v4.0 rates it 8.7 with availability-only impact, and no public exploit code or CISA KEV listing was identified at time of analysis. Because the flaw lives in middleware ordering, exploitation works against default configurations wherever the admin backend is network-reachable, and impact is confined to availability - no data disclosure or code execution.
RemediationAI
No fixed version was specified in the supplied data; JTL-Software maintains the vendor advisory at https://www.jtl-software.com/de/security/shop-maintenance-mode, which should be treated as the authoritative source for the patched JTL-Shop release and applied as soon as a fix version is listed there. Until then, the highest-value control is to remove the attack surface by restricting the administration backend to trusted networks - an IP allowlist, VPN, or reverse-proxy ACL in front of the admin path - which fully blocks the unauthenticated toggle but also blocks legitimate off-network administrator access and must be paired with an alternate admin path. A narrower, more brittle option is a WAF or reverse-proxy virtual patch that rejects requests carrying the plugin safe mode toggle parameter to the admin logout route; this can blunt automated mass scanning but risks breaking legitimate logout and safe-mode administration and can be evaded by parameter variations, so it should be treated as temporary. In parallel, monitor web logs for unexpected safe-mode toggles and verify plugin status after any suspected attempt, since a successful toggle silently deactivates all plugins, including payment and shipping integrations, and may require manual re-enablement to restore storefront functionality.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-306 (Missing Authentication for Critical Function): JTL-Shop's administration backend authentication middleware evaluates the plugin safe mode toggle parameter on the admin logout route before it verifies that the requesting user is authenticated, so the state-changing operation is reachable without credentials. The CVSS v4.0 vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N confirms network reachability, no privileges required, no user interaction, and high availability impact with no confidentiality or integrity effect; our independent assessment concurs with CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Safe mode is the mechanism JTL-Shop uses to deactivate plugins without uninstalling them, so an attacker flipping that flag silently switches off all plugin-provided functionality, including payment and shipping integrations. The affected component is tracked as cpe:2.3:a:jtl-software_gmbh:jtl-shop:*:*:*:*:*:*:*:*, a wildcard that covers the JTL-Software GmbH product line without a version constraint, meaning the flaw is not tied to a specific release in the supplied intelligence and all exposed versions should be assumed affected until the vendor advisory narrows the range.
Know when Jtl Shop gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Remote, low-complexity, pre-authentication toggle (PR:N, AC:L, AV:N) with no user interaction; impact is availability-only (A:H, C:N, I:N) as it merely disables plugins.
Primary rating from Vendor (ENISA).
CVSS VectorVendor: ENISA
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
JTL-Shop merchants face a shop-wide availability outage: a single crafted request to the administration backend can force every installed plugin - including payment and shipping integrations - into safe mode, disabling checkout-critical functionality without any data disclosure or code execution. The condition can be scripted across an entire estate of storefronts, so exposure scales with the number of internet-reachable JTL-Shop administration backends an organization operates or depends on. With no vendor patch available and no public exploit identified at time of analysis, leadership should treat this as a revenue-continuity and operational resilience risk to be contained through network and monitoring controls rather than a data-breach event.
No vendor-released patch identified at time of analysis. Interim mitigations: remove internet reachability of the JTL-Shop administration backend (IP allowlisting, VPN, or zero-trust access proxy); block or authenticate requests to the administration logout route at a WAF or reverse proxy before they reach the application; apply rate limiting and anomaly alerting on administration paths; monitor and alert on plugin safe-mode or enablement state changes; retain configuration backups of plugin state to enable rapid restoration; and maintain a plugin-dependency inventory so payment and shipping disruptions can be identified and communicated quickly.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Server-side template injection in JTL Shop 5.2.0 through 5.7.1 allows remote unauthenticated attackers to inject Smarty
Stored cross-site scripting in JTL-Shop lets unauthenticated remote attackers inject arbitrary script code through the s
EUVD-2026-100979
GHSA-xvw9-2xw4-g33x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB