What is the CVSS score of CVE-2026-45211?

CVE-2026-45211 has a CVSS 3.1 base score of 8.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L. EPSS exploitation probability: 0.0%.

Which versions of WooSquare are affected by CVE-2026-45211?

The WooSquare plugin for WooCommerce (versions ≤4.7.1) contains a blind SQL injection vulnerability that allows authenticated users with low-level WordPress privileges to extract sensitive customer…

How to fix or mitigate CVE-2026-45211?

Within 24 hours: Identify all WooCommerce installations using WooSquare plugin and document current version numbers; disable the plugin immediately if version 4.7.1 or earlier is detected. Within 7 days: Audit database access logs and user account activity for suspicious queries; review customer data access records to assess potential exposure. Within 30 days: Monitor Patchstack and APIExperts channels for patched version release; deploy vendor-released patch immediately upon availability; conduct data breach assessment if plugin was active on production systems.

WooSquare CVE-2026-45211

EUVD-2026-29453 HIGH

SQL Injection (CWE-89)

2026-05-12 Patchstack

GHSA-69rp-c53h-4qc7

SQLi WordPress

8.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

Low

Lifecycle Timeline

Analysis Generated

May 12, 2026 - 11:31 vuln.today

CVE Published

May 12, 2026 - 11:02 nvd

HIGH 8.5

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Saad Iqbal APIExperts Square for WooCommerce woosquare allows Blind SQL Injection.This issue affects APIExperts Square for WooCommerce: from n/a through <= 4.7.1.

AnalysisAI

Blind SQL injection in APIExperts Square for WooCommerce (WooSquare) plugin versions up to 4.7.1 allows authenticated attackers with low-level privileges to extract sensitive database contents including customer data, order information, and potentially administrative credentials. The vulnerability enables scope escalation from the WordPress application context to the underlying database layer (S:C in CVSS vector), representing a significant data breach risk for WooCommerce stores. Reported by Patchstack, a WordPress vulnerability intelligence provider. No active exploitation confirmed in CISA KEV at time of analysis.

Technical ContextAI

This is a blind SQL injection vulnerability (CWE-89) in the WooSquare WordPress plugin, which integrates Square payment processing with WooCommerce e-commerce platforms. Blind SQL injection occurs when user-supplied input is concatenated directly into SQL queries without proper parameterization or sanitization, and responses do not directly display query results-requiring attackers to infer data through timing analysis or boolean-based conditional responses. The CPE identifier cpe:2.3:a:saad_iqbal:apiexperts_square_for_woocommerce indicates this affects the plugin developed by Saad Iqbal. WordPress plugins commonly interact with the WordPress database (wp_posts, wp_users, wp_postmeta tables) and WooCommerce-specific tables (wp_woocommerce_order_items, wp_woocommerce_payment_tokens), making this particularly dangerous in retail environments where payment card data references or customer PII may be accessible through database queries.

RemediationAI

Immediately update APIExperts Square for WooCommerce plugin to version 4.7.2 or later if available, checking the WordPress plugin repository or the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/woosquare/vulnerability/wordpress-apiexperts-square-for-woocommerce-plugin-4-7-1-sql-injection-vulnerability for the patched release. If no patched version is available yet, implement these compensating controls: restrict the plugin's access to only trusted administrator accounts by auditing WordPress user roles and removing unnecessary shop manager or contributor privileges (trade-off: reduces operational flexibility for staff); implement a Web Application Firewall with SQL injection signatures targeting common blind SQLi patterns in POST/GET parameters (trade-off: potential false positives may block legitimate traffic); enable WordPress database query logging to detect suspicious patterns like SLEEP(), BENCHMARK(), or time-based extraction attempts (trade-off: increased database overhead and log storage requirements); consider temporarily disabling the WooSquare plugin if Square payment processing can be handled through alternative methods (trade-off: loss of payment integration functionality). Review WordPress database access logs from authentication timestamps backward to identify potential exploitation attempts.