Payment information sent to PayPal not necessarily identical to created order

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2023-23941: 0.30% estimated exploitation activity in the next 30 days; percentile 22.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact If JavaScript-based PayPal checkout methods are used (PayPal Plus, Smart Payment Buttons, SEPA, Pay Later, Venmo, Credit card), the amount and item list sent to PayPal may not be identical to the one in the created order. Patches The problem has been fixed with version 5.4.4 Workarounds Disable the aforementioned payment methods or use the Security Plugin in version = 1.0.21. References Shopware blog post

Published by the source

3 Feb 2023, 21:07 UTC

Last modified by the source

15 Feb 2023, 18:38 UTC

Source last checked

26 Oct 2026, 14:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vxpm-8hcp-qh27

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-23941

Advisory: Payment information sent to PayPal not necessarily identical to created order
IDs: CVE-2023-23941, GHSA-vxpm-8hcp-qh27
Record: https://patchnext.com/advisories/cve-2023-23941 (revision 1, source checked 26 Oct 2026, 14:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: swag/paypal 5.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist swag/paypal: affected < 5.4.4; fixed in 5.4.4

## Suggested inspection (read-only)
- Packagist swag/paypal: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on swag/paypal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vxpm-8hcp-qh27 (GitHub-reviewed advisory GHSA-vxpm-8hcp-qh27 lists affected ranges: Packagist swag/paypal >=0 <5.4.4)

Commands are suggestions: review each one before running it.