Skip to content

Improperly Implemented Security Check for Standard in PayPal Official for PrestaShop"

Moderate
clotairer published GHSA-w3w3-j3mh-3354 Jul 26, 2024

Package

Paypal (PrestaShop)

Affected versions

<= 6.4.1
<= 3.18.0

Patched versions

6.4.2
3.18.1

Description

In the module "PayPal Official" for PrestaShop 7+ release <= 6.4.1 and for PrestaShop 1.6 release <= 3.18.0, a malicious customer can confirm as "payment accepted" an order even if payment is finally declined by PayPal.

A logical weakness during the capture of a payment in case of disabled webhooks can be exploited to create an accepted order.

Possible malicious usage

  • Confirm order with a fraudulent payment support

Recommendations

  • Upgrade PayPal up to 6.4.2 or 3.18.1 according to your PrestaShop version.
  • Enable webhooks and check they are callable

Timeline

Date Action
2024-07-15 Issue discovered in a support ticket
2024-07-17 202 ecomemrce inform PayPal of a suspicious transaction
2024-07-22 Logical weakness confirmed in a testing environment
2024-07-25 Publication of this advisory with releases patch

Severity

Moderate

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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:L/UI:N/S:U/C:N/I:H/A:N

CVE ID

CVE-2024-41670

Weaknesses