Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-73475 – Authorization Bypass Allowing Fraudulent Order Completion – Drupal Commerce PayPal

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73475 is an incorrect authorization (CWE-863) vulnerability in the Commerce PayPal module for Drupal Commerce, rated Critical with a CVSS v3.1 base score of 9.1. The module fails to sufficiently validate the transaction result returned by PayPal in certain flows, allowing an unauthenticated attacker to force-browse to order-completion logic and mark a transaction as paid without ever completing payment. The issue is scoped to sites using the Payflow Link payment gateway.

Technical details

  • Root cause: Commerce PayPal does not adequately verify the payment/transaction result returned during checkout when the Payflow Link gateway is used, so the server-side code trusts client-reachable state that should require a validated PayPal response.
  • Trigger condition: An attacker directly requests (forceful browsing) the order-completion or payment-return endpoint that the module exposes after a PayPal redirect, bypassing the actual payment confirmation step.
  • Attack vector: Network-based, no authentication or user interaction required (CAPEC-87: Forceful Browsing).
  • Impact: Orders can be marked as paid/completed without any real payment being made, resulting in high confidentiality and integrity impact to order and payment state (no availability impact).

Affected software

  • Drupal Commerce PayPal (Commerce PayPal module) versions prior to 1.12.0
  • Drupal Commerce PayPal versions 2.0.0 through 2.1.2
  • Only sites configured to use the Payflow Link payment gateway are affected

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Commerce PayPal to version 8.x-1.12 (or later) if on the 1.x branch, or to version 2.1.3 (or later) if on the 2.x branch.
  • If patching is not immediately possible: No official workaround is documented by the vendor. As an interim network-layer mitigation, sites using the Payflow Link gateway should restrict or closely monitor access to PayPal payment-return/checkout-complete endpoints, and reconcile completed orders against actual PayPal transaction records until the module is upgraded.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: id="block-commerce-cart-cart", class="commerce-product-field"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge