Skip to main content
Menu
CVEs

JTL-Software JTL PayPal Checkout Plugin stored XSS in unfinished order names

JTL PayPal Checkout plugin versions 1.2.0 through 2.3.1 are affected, through its backend open orders tab. Fixed in 2.3.2.

CVE-2026-125061Published November 19, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.3.2
Who is exposed
Specific setups only

Summary

A registered customer of JTL-Shop can plant script code in the name on an unfinished PayPal order in the JTL PayPal Checkout plugin (jtl_paypal_commerce). Remotely, that script runs in the browser of an administrator who opens the open orders page, with the administrator's privileges, and could, for example, create a new administrator account.

Written by a model

Original description

The administration page "Offene Bestellungen" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the customer name of pending orders without output encoding. A registered customer (free self-registration) can submit an HTML-entity-encoded name, which is decoded to markup when the billing address of an order is written. If the PayPal payment is left unfinished, the order is listed on the page and the name is rendered as markup in the browser of an administrator who opens the page. The script code runs with the privileges of that administrator and can, for example, create a new administrator account. Guest orders are not affected, because the name is encoded again.

Who should check

Shop operators running JTL-Shop with the JTL PayPal Checkout plugin versions 1.2.0 to 2.3.1, self-hosted or through a hosting service provider.

“Du bist betroffen, wenn „JTL PayPal Checkout“ in Version 1.2.0 bis 2.3.1 installiert ist.”

jtl-software.com

What to do

  1. Check whether your setup matches what the bug needs.

    JTL PayPal Checkout plugin version 1.2.0 through 2.3.1 is installed An attacker needs a registered customer account and an abandoned PayPal payment An administrator opens the plugin's "Offene Bestellungen" (open orders) tab in the backend The unfinished order must be older than the 3-hour threshold before it appears in the tab
  2. Upgrade to a fixed version: 2.3.2.

  3. Workaround: Do not open the plugin's "Offene Bestellungen" tab until the update is applied.

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-125061 (Stored cross-site scripting in the JTL PayPal Checkout plugin), 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-125061 (entry last updated 2026-11-19):
Affected:
- JTL-Software GmbH JTL PayPal Checkout plugin (jtl_paypal_commerce): from 1.2.0, fixed in 2.3.2
Fixed versions: 2.3.2.
Conditions (all must be true for the bug to be hit):
- JTL PayPal Checkout plugin version 1.2.0 through 2.3.1 is installed (source: https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/)
- An attacker needs a registered customer account and an abandoned PayPal payment (source: https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/)
- An administrator opens the plugin's "Offene Bestellungen" (open orders) tab in the backend (source: https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/)
- The unfinished order must be older than the 3-hour threshold before it appears in the tab (source: https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
Workaround: Do not open the plugin's "Offene Bestellungen" tab until the update is applied. (source: https://www.jtl-software.com/de/security/sicherheitshinweis-paypal-checkout-plugin_xss/)
CISA KEV: CVE-2026-125061 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125061 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-paypal-checkout-plugin_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-125061
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-125061"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisoryjtl-software.com · de/security/sicherheitshinweis-paypal-checkout-plugin_xss
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-125061
RecordNVD · CVE-2026-125061

Questions about CVE-2026-125061

Is CVE-2026-125061 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?

Script code planted through an abandoned PayPal payment in a registered customer account runs when an administrator opens the plugin's "Offene Bestellungen" (open orders) tab in the backend. It runs with that administrator's privileges, so it can create a new administrator account and read data the administrator can view.

Source: jtl-software.com

Which versions are affected by CVE-2026-125061?

JTL PayPal Checkout plugin (jtl_paypal_commerce): from 1.2.0 before 2.3.2.

Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.2.0 through 2.3.1 of the JTL PayPal Checkout plugin (jtl_paypal_commerce) are affected. To check, look at the installed version of the plugin in the shop's backend plugin management, and note whether the open orders tab shows unfinished orders older than 3 hours.

Source: jtl-software.com

How do I fix CVE-2026-125061?

Update the JTL PayPal Checkout plugin to version 2.3.2. Until the update is applied, do not open the plugin's "Offene Bestellungen" tab.

Source: jtl-software.com

No corrections so far. Something wrong on this page? Report an error.