dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-45211

HIGH · 8.5 CVSS v3.1 Published 2026-05-12
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
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.

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

SQL injection vulnerability in APIExperts Square for WooCommerce plugin (woosquare) allows blind SQL injection due to improper neutralization of special elements in SQL commands. Attackers can manipulate database queries through unsanitized input, potentially exfiltrating sensitive data or modifying database contents.

MitigationUpdate the plugin to a version beyond 4.7.1 that implements proper input validation and parameterized queries. If no patched version exists, disable the plugin until a fix is available.

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. Locate the woosquare plugin installation
    Access your WordPress site via FTP or file manager, navigate to /wp-content/plugins/ and look for a folder named 'woosquare' or 'square-for-woocommerce'. If using WordPress admin, go to Plugins > Installed Plugins and search for 'Square for WooCommerce' or 'woosquare'.
    Affected if The woosquare plugin folder exists in the plugins directory
  2. Identify the installed version number
    In WordPress admin, go to Plugins > Installed Plugins, find the Square for WooCommerce entry, and note the version number displayed below the plugin name. Alternatively, open the main plugin file (usually woosquare.php or similar) in the woosquare folder and look for the 'Version' header in the plugin comment block.
    Affected if The displayed version is 4.7.1 or any earlier version
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm that the Square for WooCommerce plugin shows as 'Active' (not just installed).
    Affected if The plugin is both installed at version 4.7.1 or earlier AND currently active

You are affected if the Square for WooCommerce (woosquare) plugin is installed at version 4.7.1 or earlier and remains active on your WordPress site.

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 plugin to a version beyond 4.7.1 that implements proper input validation and parameterized queries. If no patched version exists, disable the plugin until a fix is available.

Recommended fix Moderate confidence

Version greater than 4.7.1 (verify current latest release on WordPress repository or contact vendor)

  1. 1. Check the current installed version of the APIExperts Square for WooCommerce (woosquare) plugin in your WordPress installation
  2. 2. Navigate to Plugins > WooSquare in WordPress admin or check the plugin directory to identify the exact version number
  3. 3. Visit the official WordPress plugin repository for woosquare or contact the vendor to determine if a version newer than 4.7.1 has been released with security fixes
  4. 4. If a newer version exists (greater than 4.7.1), update the plugin to the latest available version
  5. 5. After updating, verify the SQL injection vulnerability is resolved by checking plugin changelog or release notes
  6. 6. If no fixed version is available from official sources, consider disabling the plugin until a patch is released
Caveat Check plugin changelog for any breaking changes between current version and upgrade target

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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