CVE-2026-22308 in JTL-Shop
Summary
by MITRE • 11/20/2026
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified within the OnPage Composer page builder component of JTL-Shop represents a critical failure in access control mechanisms combined with insufficient output encoding, leading to both Stored Cross-Site Scripting and potential Server-Side Template Injection depending on third-party integrations. The core technical flaw stems from the preview mode functionality being triggered solely by the presence of specific request parameters rather than requiring valid authentication or session validation for backend operations. This architectural oversight allows any unauthenticated remote actor to invoke a rendering process that processes user-supplied data without verifying whether the requester possesses the necessary administrative privileges or active session tokens. Consequently, the system treats arbitrary input as trusted page content, bypassing standard security boundaries designed to protect sensitive configuration and layout structures from public exposure or manipulation.
From an operational perspective, this misconfiguration enables a variety of malicious activities ranging from client-side attacks to privilege escalation within the application environment. An attacker can craft specific URLs containing malicious script payloads that are embedded directly into the rendered page data. When a victim, such as a regular site visitor or potentially an administrator viewing their own dashboard, accesses this crafted link, the browser executes the injected JavaScript in the context of the trusted domain. This facilitates session hijacking, credential theft via keylogging scripts, or defacement of the user interface. If the target is an administrative account, the impact escalates significantly as the attacker can perform actions with elevated privileges, potentially modifying shop settings, accessing customer data, or installing further malicious modules under the guise of legitimate system operations.
The severity of this vulnerability is compounded by the lack of output encoding on several portlet properties. By failing to sanitize special characters before rendering them in HTML contexts, the application creates a classic Stored Cross-Site Scripting vector as defined by CWE-79. This allows persistent malicious code to reside within the database or configuration files and execute whenever the affected page is viewed. Furthermore, the vulnerability extends beyond simple script injection when third-party plugins are involved. Certain extensions utilize portlets that evaluate property values as templates rather than static strings. In these specific scenarios, an attacker can inject template syntax into the request parameters, which the plugin then interprets and executes server-side or within a restricted sandbox. This leads to Server-Side Template Injection, categorized under CWE-94, allowing for remote code execution or data exfiltration that goes beyond the scope of client-side script injection.
This incident maps directly to several entries in the MITRE ATT&CK framework, specifically reflecting techniques associated with Initial Access and Execution. The exploitation method aligns with Valid Accounts if an attacker compromises a session, but more critically it demonstrates Improper Privilege Management due to the bypass of authentication checks for preview functionality. The use of crafted links corresponds to Spearphishing Link tactics where social engineering is used to lure victims into triggering the vulnerability. For administrators who fall victim to such attacks, the subsequent actions may involve Defense Evasion or Credential Access depending on the payload delivered by the injected scripts.
Mitigation strategies must address both the authentication gap and the input handling deficiencies immediately. The primary remediation involves enforcing strict access control checks for any request that triggers the preview mode of OnPage Composer. Developers should ensure that backend rendering operations require a valid, authenticated session with appropriate administrative permissions before processing or outputting page data. Additionally, implementing robust output encoding is essential to neutralize special characters in all portlet properties rendered to HTML contexts, thereby preventing script execution regardless of input source. For third-party plugins exhibiting template evaluation behavior, vendors must sanitize inputs strictly and avoid interpreting raw user-supplied strings as executable code without rigorous validation against a whitelist of allowed commands or variables. Until patches are applied, administrators should restrict access to the shop backend via IP whitelisting if possible and monitor logs for unusual requests targeting preview endpoints containing encoded script tags or template delimiters.