JTL-Software JTL-Shop denial of service by lockout in the failed-login limiter
Affects JTL-Shop 5.8.0 through 5.8.3 on self-hosted or third-party-run shops; JTL-Hosting shops are not affected. Fixed in 5.8.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.8.4
- Who is exposed
- Not reported
Summary
The JTL-Shop synchronisation interface, which hands orders over to JTL-Wawi, can be blocked by an attacker. The failed-login limiter trusts the client-supplied X-Forwarded-For header, so an unauthenticated attacker can reach it remotely without logging in and trigger a lockout that they can repeat indefinitely, stopping orders from reaching JTL-Wawi. No data is disclosed and no code is executed.
Written by a model
Original description
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.
Who should check
Teams running self-hosted or third-party-hosted JTL-Shop 5.8.0 to 5.8.3 that sync orders with JTL-Wawi (ERP).
Not fixed by: An overly broad trusted proxy list lets forged client addresses through.
“Betroffen sind die Versionen 5.8.0 bis einschließlich 5.8.3.”
What to do
Upgrade to a fixed version: 5.8.4.
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-22311 (Use of a less trusted source leading to denial of service by lockout 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-22311 (entry last updated 2026-11-19):
Affected:
- JTL-Software GmbH JTL-Shop: from 5.8.0, fixed in 5.8.4
Fixed versions: 5.8.4.
Conditions (all must be true for the bug to be hit):
- JTL-Shop versions 5.8.0 through 5.8.3 (the version line where the lockout was introduced). (source: https://www.jtl-software.com/de/security/sicherheitshinweis-wawi-synchronisation_sperrung/)
- Shop is self-hosted or run by a third-party service provider; shops on JTL-Hosting are not affected. (source: https://www.jtl-software.com/de/security/sicherheitshinweis-wawi-synchronisation_sperrung/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-22311 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-22311 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-wawi-synchronisation_sperrung/
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-22311
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-22311"}.Affected versions
- JTL-Software GmbH JTL-ShopFrom 5.8.0 · fixed in 5.8.4
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | jtl-software.com · de/security/sicherheitshinweis-wawi-synchronisation_sperrung |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-22311 |
| Record | NVD · CVE-2026-22311 |
Questions about CVE-2026-22311
Is CVE-2026-22311 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 unauthenticated attacker can block the ERP synchronisation interface and keep renewing the lockout. Orders are still accepted by the shop but are not passed on to the ERP system (JTL-Wawi). No data is read and no code is executed.
Source: jtl-software.com
Which versions are affected by CVE-2026-22311?
JTL-Shop: from 5.8.0 before 5.8.4.
Source: cve.now feed data
Am I affected, and how do I check?
JTL-Shop versions 5.8.0 through 5.8.3 are affected. Shops run on JTL-Hosting are not affected, while self-hosted or third-party-run shops are in scope. To check, look at the shop version in the shop's administration and confirm whether the shop is hosted by JTL-Hosting.
Source: jtl-software.com
How do I fix CVE-2026-22311?
Upgrade to JTL-Shop 5.8.4, which contains the fix.
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.