What is the CVSS score of EUVD-2026-48112?

EUVD-2026-48112 has a CVSS 3.1 base score of 5.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.2%.

Shiptastic for WooCommerce EUVD-2026-48112

| CVE-2026-65501 MEDIUM

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-07-23 Patchstack

GHSA-jm5r-8xqc-j74x

WordPress Authentication Bypass Wordpress Plugin Shiptastic For Woocommerce

5.3

CVSS 3.1 · Vendor: Patchstack

Severity by source

Vendor (Patchstack) PRIMARY

5.3 MEDIUM

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

vuln.today AI

5.3 MEDIUM

Unauthenticated network IDOR with no user interaction yields only low confidentiality exposure; zero integrity or availability impact confirmed by description.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 23, 2026 - 13:18 vuln.today

CVE Published

Jul 23, 2026 - 11:19 cve.org

MEDIUM 5.3

DescriptionCVE.org

Unauthenticated Insecure Direct Object References (IDOR) in Shiptastic for WooCommerce <= 5.1.0 versions.

AnalysisAI

Shiptastic for WooCommerce plugin (versions ≤ 5.1.0) by Vendidero exposes an Insecure Direct Object Reference (IDOR) flaw that allows unauthenticated remote attackers to access shipment or order objects belonging to other users by manipulating predictable reference parameters. The CVSS vector (PR:N/UI:N/AV:N) confirms no authentication or user interaction is required to trigger the issue, though impact is bounded to low confidentiality disclosure with no integrity or availability consequence. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.

Technical ContextAI

CWE-639 (Authorization Through User-Controlled Key) describes a class of flaw where an application uses attacker-supplied input - typically an order ID, shipment reference number, or tracking token - to directly retrieve backend objects without verifying that the requesting party is authorized to access that specific resource. In WooCommerce-based plugins, this commonly manifests in REST API endpoints, order-status tracking pages, or AJAX handlers that accept an object identifier (e.g., ?order_id=1234) and return data without confirming the requesting session owns that record. The CPE string cpe:2.3:a:vendidero:shiptastic_for_woocommerce:*:*:*:*:*:*:*:* confirms all releases of the Vendidero-authored Shiptastic for WooCommerce plugin up to and including 5.1.0 are affected. The tag 'Authentication Bypass' from Patchstack indicates the authorization check is either absent or trivially circumvented, not merely weak.

RemediationAI

The primary remediation is to update the Shiptastic for WooCommerce plugin beyond version 5.1.0 via the WordPress plugin dashboard or the WordPress.org plugin repository. The exact patched version number is not independently confirmed from available data - consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/shiptastic-for-woocommerce/vulnerability/wordpress-shiptastic-for-woocommerce-plugin-5-1-0-insecure-direct-object-references-idor-vulnerability) and the official WordPress plugin page for the current release. If an update is not immediately available, consider temporarily disabling the plugin to eliminate the attack surface - note this will remove associated shipping functionality. As a compensating control, restrict access to the affected endpoints via web application firewall (WAF) rules that require authenticated sessions for any order or shipment object retrieval, though the specific endpoint path should be confirmed from the Patchstack advisory before configuring WAF rules. Operators subject to GDPR or similar data-protection law should evaluate whether the exposure window constitutes a reportable breach.