The WooCommerce PayPal Payments plugin for WordPress is vulnerable to Sensitive Information Disclosure due to an Insecure Direct Object Reference in all versions up to, and including, 3.3.2 via the `enqueue_paypal_insights_script_on_order_received()` function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to obtain sensitive order information including order keys, which can then be leveraged to access full customer billing details (name, email, phone, address) via the WooCommerce Store API within a 10-minute grace period after order creation.
Security readout for executives and security teams
Plain-English summary
Affected online stores may expose customer billing details to unauthenticated attackers. A missing authorization check can reveal an order key, which may permit access to names, email addresses, phone numbers, and postal addresses shortly after an order is created.
Executive priority
Schedule prompt remediation for affected commerce sites. Although rated moderate, the issue exposes personal customer data without authentication and can create privacy, fraud, and reputational consequences. Escalate priority where order volume is high or public endpoints lack additional protections.
Technical view
WooCommerce PayPal Payments through 3.3.2 contains a CWE-639 insecure direct object reference in `enqueue_paypal_insights_script_on_order_received()`. A user-controlled key is insufficiently validated, allowing unauthenticated disclosure of order information. Exposed order keys can access full billing details through the WooCommerce Store API during a 10-minute post-creation grace period.
Likely exposure
Internet-accessible WordPress stores using WooCommerce PayPal Payments version 3.3.2 or earlier are potentially exposed, particularly while processing new orders. Exposure depends on the affected functionality being active and an attacker reaching relevant public endpoints during the limited grace period.
Exploitation context
The weakness is remotely reachable without authentication, privileges, or user interaction. The supplied CVSS score is 5.3. The source bundle does not report active exploitation, and the CVE is not listed as known exploited in the supplied KEV signal.
Researcher notes
The documented chain requires first obtaining order information, including an order key, then accessing billing details through the Store API within 10 minutes of order creation. The supplied references include source and changeset evidence, but provide no confirmed exploitation telemetry or detailed indicators of compromise.
Mitigation direction
Upgrade WooCommerce PayPal Payments beyond version 3.3.2 after confirming current vendor guidance and compatibility.
Prioritize stores processing customer orders or exposing WooCommerce endpoints to the internet.
Apply compensating access controls only if vendor-supported and operationally safe.
Review privacy and incident-response procedures for possible customer billing-data exposure.
Validation and detection
Inventory all WordPress sites and record the installed WooCommerce PayPal Payments version.
Confirm no production instance remains on version 3.3.2 or earlier.
Verify the updated plugin is active and checkout functionality remains operational.
Review web and Store API logs for unusual access around newly created orders.
Confirm monitoring covers unauthorized access to order and customer billing information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.