dbcve.org
Xstore CoreWordPress extension · 8theme

CVE-2024-33551

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-29
Fix available
A fix is available. Upgrade to 5.3.9 or later.
See remediation →
100/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in 8theme XStore Core allows SQL Injection.This issue affects XStore Core: from n/a through 5.3.5.

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

SQL Injection vulnerability in 8theme XStore Core plugin allows attackers to inject malicious SQL commands via unsanitized input in database queries. This critical flaw (CVSS 9.8) affects all versions up to 5.3.5 and can be exploited remotely without authentication to extract, modify, or delete database contents.

MitigationUpgrade XStore Core to version 5.3.6 or later which contains the patched code. If immediate patching is not possible, implement web application firewall (WAF) rules to block SQL injection payloads as a temporary mitigation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Xstore CoreWordPress extension
Affected:< 5.3.9

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify XStore Core plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the 'xstore-core' folder.
    Affected if The XStore Core plugin folder exists in the WordPress installation.
  2. Determine installed XStore Core version
    In WordPress admin, go to Plugins > Installed Plugins and find the XStore Core entry to view its version number. Alternatively, check the main plugin file (usually xstore-core.php) for the 'Version' header in the plugin comments.
    Affected if A version number is displayed and is lower than 5.3.9.
  3. Check WordPress plugins database table for plugin record
    Run SQL query: SELECT option_value FROM wp_options WHERE option_name = 'xstore_core_version' OR option_name LIKE '%xstore%version%'; This checks the database-stored version if different from file header.
    Affected if A version value lower than 5.3.9 is returned.
  4. Inspect plugin files for vulnerable query code
    Search within the /wp-content/plugins/xstore-core/ directory for raw SQL query patterns without prepare() statements: grep -r '$wpdb->query' or grep -r '$wpdb->get_results' (examine context to see if user input is used without sanitization).
    Affected if Database queries directly incorporate request parameters or user input without using $wpdb->prepare() or equivalent sanitization.

The environment is affected if the XStore Core plugin is installed with any version below 5.3.9.

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
Upgrade available Upgrade to 5.3.9 or later
Fixed in 5.3.9
Interim mitigation

Upgrade XStore Core to version 5.3.6 or later which contains the patched code. If immediate patching is not possible, implement web application firewall (WAF) rules to block SQL injection payloads as a temporary mitigation.

Recommended fix High confidence

5.3.9 or later

  1. Create a complete backup of the WordPress website and database before performing any updates
  2. Navigate to the WordPress admin panel and locate the XStore Core plugin or theme management area
  3. Update XStore Core to version 5.3.9 or the latest available version
  4. Verify the update completed successfully without errors
  5. Test the website functionality to ensure the update did not break any features

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

Fix this in Xstore Core Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33551 — 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-2024-33551 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