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

EUVD-2026-41309 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%.

Kit for WooCommerce EUVD-2026-41309

| CVE-2026-57753 MEDIUM

Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497)

2026-07-02 Patchstack

GHSA-q6f8-4vjv-w4qf

WordPress Information Disclosure Wordpress Plugin Kit Formerly Convertkit 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

Network-accessible endpoint with no authentication barrier; limited confidentiality impact only, with no integrity or availability effect confirmed.

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 02, 2026 - 12:30 vuln.today

CVE Published

Jul 02, 2026 - 11:15 cve.org

MEDIUM 5.3

DescriptionCVE.org

Unauthenticated Sensitive Data Exposure in Kit (formerly ConvertKit) for WooCommerce <= 2.1.5 versions.

AnalysisAI

Unauthenticated sensitive data exposure in the Kit (formerly ConvertKit) for WooCommerce WordPress plugin versions 2.1.5 and below allows remote unauthenticated attackers to access sensitive information without any credentials or user interaction. The vulnerability is classified under CWE-497, indicating the plugin inadvertently surfaces system or application-level sensitive data to an unauthorized control sphere - likely including API keys, subscriber data, or configuration secrets tied to the Kit email marketing integration. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Technical ContextAI

The affected component is the Kit (formerly ConvertKit) for WooCommerce WordPress plugin authored by nathanbarry, identified by CPE cpe:2.3:a:nathanbarry:kit_(formerly_convertkit)_for_woocommerce:*:*:*:*:*:*:*:*. This plugin integrates WooCommerce e-commerce stores with the Kit (formerly ConvertKit) email marketing platform, typically handling subscriber synchronization, API credentials, and customer purchase event data. CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) indicates the root cause is improper access control over an endpoint or response that returns data beyond what an unauthenticated caller should be permitted to receive - common patterns include unprotected REST API endpoints, exposed admin-ajax.php handlers, or debug/status pages that omit authentication checks. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms this is exploitable remotely over HTTP with no complexity barrier and no authentication.

RemediationAI

The primary remediation is to update the Kit for WooCommerce plugin to a version above 2.1.5 via the WordPress plugin dashboard or WP-CLI. No exact fixed version number is independently confirmed in the available input data - administrators should consult the official WordPress plugin repository for the latest release and verify via the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/convertkit-for-woocommerce/vulnerability/wordpress-kit-formerly-convertkit-for-woocommerce-plugin-2-1-5-sensitive-data-exposure-vulnerability. If an immediate patch cannot be applied, a compensating control is to temporarily deactivate the plugin through the WordPress admin panel, noting this will halt Kit subscriber synchronization and email marketing event triggers. Operators may also use a web application firewall (WAF) rule to block unauthenticated access to the plugin's specific REST or admin-ajax endpoints - though identifying the exact endpoint requires further vendor disclosure. Rotating the Kit API key stored in the plugin's settings is advisable as a precautionary measure regardless of patch status, since the exposed data may have already included credential material.