dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3326

HIGH · 8.6 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Xstore WordPress theme before version 9.7.3 contains an unauthenticated SQL injection vulnerability. An AJAX action accessible to unauthenticated users fails to properly sanitize and escape a parameter before using it in a SQL query, allowing remote attackers to inject malicious SQL commands.

MitigationUpdate the Xstore theme to version 9.7.3 or later. If immediate updating is not possible, disable the affected AJAX action via .htaccess or a security plugin until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Xstore theme installation
    Check the wp-content/themes/etBuilder_core or wp-content/themes/xstore directory for the theme files. Look for a style.css file or version.php that contains version information.
    Affected if The Xstore theme files are present in the WordPress themes directory.
  2. Read the installed Xstore theme version
    Open the style.css file in the theme directory and locate the 'Version:' declaration in the theme header comment. Alternatively, check version.php or theme.json for the version string.
    Affected if The version number found is below 9.7.3 (e.g., 9.7.2, 9.6.x, etc.).
  3. Identify the vulnerable AJAX action endpoint
    Search the theme files for AJAX action handlers, specifically looking for functions hooked to wp_ajax_ or wp_ajax_nopriv_ that handle user-supplied parameters without proper sanitization. Common patterns: add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...').
    Affected if An AJAX handler exists that processes request parameters directly into SQL queries without prepared statements or escaping.
  4. Test unauthenticated access to the AJAX endpoint
    If identified, send a crafted request to the AJAX endpoint (typically /wp-admin/admin-ajax.php) with the vulnerable parameter to observe if SQL error messages are returned or if the query can be manipulated.
    Affected if The AJAX endpoint responds to unauthenticated requests and the parameter can be injected with SQL syntax.

The environment is affected if the Xstore theme version is below 9.7.3 and the vulnerable unauthenticated AJAX action handler is accessible and processes SQL queries without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Xstore theme to version 9.7.3 or later. If immediate updating is not possible, disable the affected AJAX action via .htaccess or a security plugin until the update can be applied.

Recommended fix High confidence

Xstore theme version 9.7.3

  1. Create a full backup of your WordPress site (files and database) before making any changes
  2. Update the Xstore WordPress theme to version 9.7.3 or later through the WordPress dashboard (Appearance > Themes) or via the vendor's update mechanism
  3. Verify the theme version has been successfully updated to 9.7.3 or higher in the WordPress admin panel
  4. Test critical site functionality (especially AJAX-based features that were vulnerable) to ensure the update did not break existing functionality
  5. Review any custom code or child theme modifications that may interact with the updated theme
Caveat Theme updates may temporarily affect customizations or child theme functionality; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3326 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data