This SQL injection in a WooCommerce extension carries a CVSS 7.6 precisely because 'administrator-only' is not a security boundary — it's an access control check. In multisite and hosted WooCommerce environments, admin accounts are customer accounts: compromised via phishing, credential stuffing, or shared-hosting privilege escalation. The developers likely assumed 'only admins reach this function' was sufficient security reasoning. It wasn't. The unescaped SQL lives in whatever admin utility, AJAX handler, or bulk-action processor handles the vulnerable input — these are the forgotten sediment layers of plugin development, the boring code that gets marked 'stable' and never reviewed again. The vulnerability class persists because $wpdb->prepare() has existed since WordPress 2.0, yet the plugin used $wpdb->query() with string interpolation. That's not a knowledge gap — it's a workflow gap: either a developer wrote unsafe SQL during a feature sprint with no reviewer catch, or inherited code from an acquisition that never underwent security re-audit. Check your composer.json or plugin headers to trace whether this code arrived via acquisition. Your immediate actions: (1) confirm the plugin version and whether your environment auto-updates; (2) grep the plugin codebase for $wpdb->query( with string concatenation — that's your indicator of systemic risk beyond this single CVE; (3) if the plugin was acquired, flag it for full query-layer refactoring, not just this patch — inherited SQL injection debt tends to be compound. The CVSS 7.6 accounts for the blast radius: a compromised admin in WooCommerce is a direct pivot to customer PII, order history, and payment tokens across every merchant on that installation.
CVE-2026-59537
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 · uneditedAdministrator SQL Injection in Sender – Newsletter, SMS and Email Marketing Automation for WooCommerce <= 2.10.22 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 analysisUser input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.
General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59537 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis SQL injection in a WooCommerce extension carries a CVSS 7.6 precisely because 'administrator-only' is not a security boundary — it's an access control check. In multisite and hosted WooCommerce environments, admin accounts are customer accounts: compromised via phishing, credential stuffing, or shared-hosting privilege escalation. The developers likely assumed 'only admins reach this function' was sufficient security reasoning. It wasn't. The unescaped SQL lives in whatever admin utility, AJAX handler, or bulk-action processor handles the vulnerable input — these are the forgotten sediment layers of plugin development, the boring code that gets marked 'stable' and never reviewed again. The vulnerability class persists because $wpdb->prepare() has existed since WordPress 2.0, yet the plugin used $wpdb->query() with string interpolation. That's not a knowledge gap — it's a workflow gap: either a developer wrote unsafe SQL during a feature sprint with no reviewer catch, or inherited code from an acquisition that never underwent security re-audit. Check your composer.json or plugin headers to trace whether this code arrived via acquisition. Your immediate actions: (1) confirm the plugin version and whether your environment auto-updates; (2) grep the plugin codebase for $wpdb->query( with string concatenation — that's your indicator of systemic risk beyond this single CVE; (3) if the plugin was acquired, flag it for full query-layer refactoring, not just this patch — inherited SQL injection debt tends to be compound. The CVSS 7.6 accounts for the blast radius: a compromised admin in WooCommerce is a direct pivot to customer PII, order history, and payment tokens across every merchant on that installation.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59537 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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