Skip to content

Sylius PayPal Plugin allows unauthorized access to Credit card form, exposing payer name and not requiring 3DS

High severity GitHub Reviewed Published Oct 5, 2021 in Sylius/PayPalPlugin • Updated Jan 27, 2023

Package

composer sylius/paypal-plugin (Composer)

Affected versions

>= 1.0.0, < 1.2.4
>= 1.3.0, < 1.3.1

Patched versions

1.2.4
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

References

@Zales0123 Zales0123 published to Sylius/PayPalPlugin Oct 5, 2021
Reviewed Oct 5, 2021
Published by the National Vulnerability Database Oct 5, 2021
Published to the GitHub Advisory Database Oct 6, 2021
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.194%
(58th percentile)

CVE ID

CVE-2021-41120

GHSA ID

GHSA-25fx-mxc2-76g7

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.