dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-41670

HIGH · 7.5 CVSS v3.1 Published 2024-07-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the module "PayPal Official" for PrestaShop 7+ releases prior to version 6.4.2 and for PrestaShop 1.6 releases prior to version 3.18.1, a malicious customer can confirm 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. This could allow a threat actor to confirm an order with a fraudulent payment support. Versions 6.4.2 and 3.18.1 contain a patch for the issue. Additionally, users enable webhooks and check they are callable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PayPal Official module for PrestaShop contains a logic flaw in the payment capture flow. When webhooks are disabled, the module fails to properly validate PayPal's payment response, allowing a malicious customer to confirm an order even after PayPal has declined the payment. This enables creation of accepted orders with fraudulent payment instruments.

MitigationUpdate the PayPal Official module to version 6.4.2 (PrestaShop 7+) or 3.18.1 (PrestaShop 1.6). Additionally, ensure webhooks are enabled and verified as callable to prevent exploitation of this logic weakness.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify PayPal Official module version
    In PrestaShop admin, go to Modules > Module Manager and search for 'PayPal Official' or 'paypal'. Note the installed version number.
    Affected if Version is below 6.4.2 for PrestaShop 7+ or below 3.18.1 for PrestaShop 1.6.
  2. Check webhook configuration in PayPal module settings
    Access the PayPal Official module configuration panel in PrestaShop admin. Look for a webhook or IPN (Instant Payment Notification) settings section. Determine whether webhooks are enabled or disabled.
    Affected if Webhooks are disabled.
  3. Verify webhook endpoint accessibility
    If webhooks are enabled, confirm the webhook endpoint URL is publicly accessible and not returning errors. Check the PayPal module logs or webhook status if available in the admin panel.
    Affected if Webhooks are enabled but the endpoint is unreachable or not responding.
  4. Confirm payment validation behavior for declined transactions
    Review the module's payment response handling. In the module configuration or documentation, check if there is explicit validation of PayPal payment status (Completed vs Declined) before order confirmation.
    Affected if The module does not validate payment response status from PayPal when webhooks are disabled.

You are affected if you use the PayPal Official module with webhooks disabled, or with webhooks enabled but unreachable, and your module version is below the patched releases (6.4.2 for PS7+ or 3.18.1 for PS1.6).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the PayPal Official module to version 6.4.2 (PrestaShop 7+) or 3.18.1 (PrestaShop 1.6). Additionally, ensure webhooks are enabled and verified as callable to prevent exploitation of this logic weakness.

Recommended fix High confidence

PayPal Official module 6.4.2 (PrestaShop 7+) or 3.18.1 (PrestaShop 1.6)

  1. Upgrade the PayPal Official module to version 6.4.2 or higher if running PrestaShop 7+
  2. Upgrade the PayPal Official module to version 3.18.1 or higher if running PrestaShop 1.6
  3. After upgrading, enable webhooks in the PayPal module configuration panel
  4. Verify that webhooks are callable and properly reaching the PrestaShop endpoint
  5. Test a transaction to confirm orders are only created when payment is successfully captured

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41670 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data