JTL-Software JTL-Shop stored XSS in 404 redirect logging
Only affects JTL-Shop up to 5.8.3 (traceable to 4.03.0) with saving of requests to non-existent pages (404) enabled (redirect_save_404 = Y). Fixed in 5.8.4, 5.7.6, 5.6.6 and 5.5.5.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.8.4, 5.7.6, 5.6.6, 5.5.5
- Who is exposed
- Specific setups only
Summary
JTL-Software GmbH's JTL-Shop has a stored cross-site scripting flaw that a remote attacker can exploit without logging in, using a single request when the setting for saving requests to non-existent pages (404) is enabled. The stored script runs in the browser of an administrator who opens the affected redirect, letting the attacker perform actions with that administrator's privileges.
Written by a model
Original description
When the setting for saving requests to non-existent pages (404) is enabled, JTL-Shop stores the raw requested URL in its redirect table, and the administration backend renders it without output encoding in the form used to edit a redirect. An unauthenticated remote attacker can store script code with a single request, which is executed in the browser session of an administrator who opens the affected redirect, allowing actions to be performed with the administrator's privileges. The setting is disabled by default in new installations but may still be enabled in older ones.
Who should check
Teams running JTL-Shop up to 5.8.3 with redirect_save_404 set to Y, including self-hosted shops and hosting providers. Versions 5.0 to 5.4 and 4.x get no patch.
Not fixed by: Disabling 404 saving is only a stopgap and does not replace the update.
“Betroffen sind alle Versionen bis einschließlich 5.8.3, sofern die Einstellung zum Speichern von 404-Aufrufen aktiv ist.”
What to do
Check whether your setup matches what the bug needs.
JTL-Shop versions up to 5.8.3 (traceable to 4.03.0) are affected The setting for saving requests to non-existent pages (404) is enabled (redirect_save_404 = Y)Upgrade to a fixed version: 5.8.4, 5.7.6, 5.6.6, 5.5.5.
Workaround: Turn off 404 saving by setting redirect_save_404 to N. Existing entries may remain.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-22310 (Stored cross-site scripting in JTL-Shop), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-22310 (entry last updated 2026-11-19):
Affected:
- JTL-Software GmbH JTL-Shop: from 5.8.0, fixed in 5.8.4; from 5.7.0, fixed in 5.7.6; from 5.6.0, fixed in 5.6.6; from 5.5.0, fixed in 5.5.5
Fixed versions: 5.8.4, 5.7.6, 5.6.6, 5.5.5.
Conditions (all must be true for the bug to be hit):
- JTL-Shop versions up to 5.8.3 (traceable to 4.03.0) are affected (source: https://www.jtl-software.com/de/security/sicherheitshinweis-404-weiterleitungen_xss/)
- The setting for saving requests to non-existent pages (404) is enabled (redirect_save_404 = Y) (source: https://www.jtl-software.com/de/security/sicherheitshinweis-404-weiterleitungen_xss/)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
Workaround: Turn off 404 saving by setting redirect_save_404 to N. Existing entries may remain. (source: https://www.jtl-software.com/de/security/sicherheitshinweis-404-weiterleitungen_xss/)
CISA KEV: CVE-2026-22310 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-22310 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.jtl-software.com/de/security/sicherheitshinweis-404-weiterleitungen_xss/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-22310
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-22310"}.Affected versions
- JTL-Software GmbH JTL-ShopFrom 5.8.0 · fixed in 5.8.4; From 5.7.0 · fixed in 5.7.6; From 5.6.0 · fixed in 5.6.6; From 5.5.0 · fixed in 5.5.5
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9/10CVSS 8.0, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | jtl-software.com · de/security/sicherheitshinweis-404-weiterleitungen_xss |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-22310 |
| Record | NVD · CVE-2026-22310 |
Questions about CVE-2026-22310
Is CVE-2026-22310 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An attacker can run script in an administrator's browser session. That script can send backend requests with the administrator's rights and read any data the administrator can view, such as customer data.
Source: jtl-software.com
Which versions are affected by CVE-2026-22310?
JTL-Shop: from 5.8.0 before 5.8.4; from 5.7.0 before 5.7.6; from 5.6.0 before 5.6.6; from 5.5.0 before 5.5.5.
Source: cve.now feed data
Am I affected, and how do I check?
Shop versions up to 5.8.3 are affected, traceable to 4.03.0. Only shops where saving requests to non-existent pages (404) is enabled are affected, which is the setting redirect_save_404 = Y. Check the installed shop version and the value of redirect_save_404.
Source: jtl-software.com
How do I fix CVE-2026-22310?
Upgrade to the fixed version for your release line: 5.8.4, 5.7.6, 5.6.6 or 5.5.5. Until then, set redirect_save_404 to N, though existing entries may remain.
Source: jtl-software.com
Related
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-123058Missing authentication for critical function in JTL-Shop
- CVE-2026-103905Unauthenticated Plugin Safe Mode Toggle Vulnerability in JTL-Shop
- CVE-2026-103904Stored XSS Vulnerability in JTL-Shop
- CVE-2026-125060Authorization bypass through user-controlled key in JTL-Shop
No corrections so far. Something wrong on this page? Report an error.