CVE-2026-3326
Received Received - Intake
SQL Injection in Xstore WordPress Theme

Publication date: 2026-06-10

Last updated on: 2026-06-10

Assigner: WPScan

Description
The Xstore WordPress theme before 9.7.3 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-10
Last Modified
2026-06-10
Generated
2026-06-10
AI Q&A
2026-06-10
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
xtheme xstore to 9.7.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The vulnerability exists in the XStore WordPress theme versions before 9.7.3. It is a SQL injection flaw caused by the theme not properly sanitizing and escaping a parameter used in a SQL query. This parameter is processed via an AJAX action that is accessible to unauthenticated users, meaning anyone can exploit it without logging in.

An attacker can inject malicious SQL code through this flaw, which can manipulate the database. A proof of concept showed that a crafted request could cause a delayed response by using a SQL SLEEP command, demonstrating control over the SQL query execution.

Impact Analysis

This vulnerability can have serious impacts because it allows attackers to execute arbitrary SQL commands on the database without authentication. This can lead to unauthorized data access, data manipulation, or denial of service by causing delays or crashes.

Since the exploit requires the XStore theme, XStore Core Plugin, and WooCommerce Plugin to be installed, websites using this combination are at risk. The vulnerability is classified as high severity with a CVSS score of 8.6.

Detection Guidance

This vulnerability can be detected by sending a crafted AJAX request to the vulnerable XStore theme that includes a SQL injection payload. A proof of concept involves sending a request that triggers a SQL SLEEP(5) command, causing a delayed response of around 11 seconds or more.

To detect the vulnerability, you can monitor for unusually delayed responses from AJAX endpoints related to the XStore theme or use tools like curl or wget to send the crafted request and observe the response time.

  • Use curl to send a test request with a SQL injection payload and check for delayed response times.
  • Example command: curl -i -X POST 'https://yourwordpresssite.com/wp-admin/admin-ajax.php' --data 'action=your_ajax_action&param=1%27%20OR%20SLEEP(5)%23'
Mitigation Strategies

The immediate step to mitigate this vulnerability is to update the XStore WordPress theme to version 9.7.3 or later, where the issue has been fixed.

Ensure that the XStore Core Plugin and WooCommerce Plugin are also installed and updated as required, since the exploit depends on these components.

Additionally, consider restricting access to AJAX endpoints or implementing web application firewall (WAF) rules to block suspicious SQL injection attempts until the update can be applied.

Compliance Impact

The vulnerability is a high severity SQL injection flaw that allows unauthenticated attackers to inject malicious SQL code via an AJAX action in the XStore WordPress theme. Such vulnerabilities can lead to unauthorized access or manipulation of sensitive data stored in the database.

While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, SQL injection vulnerabilities generally pose a risk to data confidentiality and integrity, which are critical requirements under these regulations.

If exploited, this vulnerability could lead to unauthorized data exposure or alteration, potentially resulting in non-compliance with data protection regulations that mandate safeguarding personal and sensitive information.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-3326. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart