dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-52700

HIGH · 8.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Subscriber SQL Injection in WCMultiShipping <= 3.0.2 versions.

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 · moderate confidence

A SQL injection vulnerability exists in the WCMultiShipping WooCommerce plugin (versions 3.0.2 and below). The vulnerability is present in subscriber-level functionality, allowing authenticated users with subscriber privileges to inject malicious SQL queries through unsanitized input parameters.

MitigationUpgrade WCMultiShipping to a version newer than 3.0.2. If no patch is available, implement parameterized queries or prepared statements for all database operations that handle user input, and add proper input validation and sanitization.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 WCMultiShipping plugin is installed
    Check the WordPress plugins directory for wcmultishipping folder: /wp-content/plugins/wcmultishipping/ or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if WCMultiShipping plugin is present in the WordPress installation
  2. Check installed WCMultiShipping version
    Open the main plugin file (usually wcmultishipping.php or version.php in /wp-content/plugins/wcmultishipping/) and look for the Version header in the plugin comment block, or check the plugins page in WordPress admin
    Affected if Version is 3.0.2 or below, or if a version number cannot be determined but the plugin is installed and was downloaded before the patch
  3. Confirm subscriber-level user accounts exist
    Navigate to WordPress admin > Users and review user roles, or query the wp_usermeta table for users with wp_capabilities containing 'subscriber'
    Affected if Any subscriber-level user accounts exist in the WordPress installation
  4. Identify plugin features accessible to subscriber role
    Review the plugin code for functions hooking into WordPress actions/filters and check if any are accessible to subscribers (capability checks using current_user_can('read') or similar low-privilege checks)
    Affected if The plugin exposes any functionality accessible to users with subscriber role without higher privilege checks
  5. Locate unsanitized input parameters in subscriber-accessible code
    Search plugin PHP files for $_GET, $_POST, or $_REQUEST usage within functions accessible to subscribers, and check if these inputs are used directly in SQL queries without prepare() or esc_sql()
    Affected if User input parameters from $_GET, $_POST, or $_REQUEST are used in database queries without proper sanitization or prepared statements in subscriber-accessible functions

If WCMultiShipping version 3.0.2 or below is installed AND subscriber users exist AND the plugin has subscriber-accessible functionality with unsanitized input used in SQL queries, the environment is affected by CVE-2026-52700.

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

Upgrade WCMultiShipping to a version newer than 3.0.2. If no patch is available, implement parameterized queries or prepared statements for all database operations that handle user input, and add proper input validation and sanitization.

Recommended fix Moderate confidence

WCMultiShipping version greater than 3.0.2 (e.g., 3.0.3 or latest stable release)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate WCMultiShipping in the plugins list.
  4. 4. Check the current installed version to confirm it is 3.0.2 or below.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. After updating, verify the plugin version has changed from 3.0.2 to a newer release.
  7. 7. Test critical functionality (checkout, shipping calculations) to ensure the update did not break existing features.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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