GitHub Advisoryadvisory · Packagist

GHSA-25fx-mxc2-76g7 Sylius PayPal Plugin allows unauthorized access to Credit card form, exposing payer name and not requiring 3DS

HIGH Published 2021-10-06 Modified 2022-08-15 Official page ↗
Aliases
CVE-2021-41120
Ecosystem
Packagist
Packages
sylius/paypal-plugin
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-200, CWE-639
Reviewed
2021-10-05

Affected packages

• Packagist sylius/paypal-plugin: >= 1.0.0, < 1.2.4 → fixed in 1.2.4 • Packagist sylius/paypal-plugin: >= 1.3.0, < 1.3.1 → fixed in 1.3.1

Description

Impact URL to the payment page done after checkout was created with autoincremented payment id (`/pay-with-paypal/{id}`) and therefore it was easy to access for anyone, not even the order's customer. The problem was, the Credit card form has prefilled "credit card holder" field with the Customer's first and last name. Additionally, the mentioned form did not require a 3D Secure authentication, as well as did not checked the result of the 3D Secure authentication. Patches The problem has been patched in Sylius/PayPalPlugin 1.2.4 and 1.3.1 Workarounds One can override a `sylius_paypal_plugin_pay_with_paypal_form` route and change its URL parameters to (for example) `{orderToken}/{paymentId}`, then override the `Sylius\PayPalPlugin\Controller\PayWithPayPalFormAction` service, to operate on the payment taken from the repository by these 2 values. It would also require usage of custom repository method. Additionally, one could override the `@SyliusPayPalPlugin/payWithPaypal.html.twig` template, to add `contingencies: ['SCA_ALWAYS']` line in `hostedFields.submit(...)` function call (line 421). It would then have to be handled in the function callback. For more information If you have any questions or comments about this advisory: • Open an issue in Sylius/PayPalPlugin issues • Email us at security at sylius dot com

Related

Alias · CVE (1)

  • CVE-2021-41120 sylius/paypal-plugin is a paypal plugin for the Sylius development platform. vulnerability

Weakness · CWE (2)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key weakness

References