JTL-Software JTL-Shop up to 5.5.4/5.6.5/5.7.5/5.8.3 Checkout access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00+ |
Summary
A vulnerability identified as critical has been detected in JTL-Software JTL-Shop up to 5.5.4/5.6.5/5.7.5/5.8.3. This affects an unknown part of the component Checkout. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2026-125060. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in JTL-Software JTL-Shop up to 5.5.4/5.6.5/5.7.5/5.8.3. This issue affects some unknown functionality of the component Checkout. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at jtl-software.com. The identification of this vulnerability is CVE-2026-125060 since 11/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 5.5.5, 5.6.6, 5.7.6 or 5.8.4 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 5.5.0
- 5.5.1
- 5.5.2
- 5.5.3
- 5.5.4
- 5.6.0
- 5.6.1
- 5.6.2
- 5.6.3
- 5.6.4
- 5.6.5
- 5.7.0
- 5.7.1
- 5.7.2
- 5.7.3
- 5.7.4
- 5.7.5
- 5.8.0
- 5.8.1
- 5.8.2
- 5.8.3
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (ENISA): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: JTL-Shop 5.5.5/5.6.6/5.7.6/5.8.4
Timeline
11/09/2026 CVE reserved11/19/2026 Advisory disclosed
11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Advisory: jtl-software.comStatus: Confirmed
CNA: ENISA
CVE: CVE-2026-125060 (🔒)
GCVE (CVE): GCVE-0-2026-125060
GCVE (VulDB): GCVE-100-440057
Entry
Created: 11/19/2026 12:57Changes: 11/19/2026 12:57 (75)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.