dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-1651

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the 'workflow_ids' parameter in all versions up to, and including, 5.9.16 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Email Subscribers by Icegram Express WordPress plugin fails to properly sanitize and escape the 'workflow_ids' parameter, allowing authenticated administrators to inject arbitrary SQL commands. The vulnerability stems from insufficient input validation combined with the absence of prepared statements in the vulnerable SQL query, enabling database data exfiltration.

MitigationUpdate the plugin to version 5.9.17 or later which contains proper input sanitization and uses prepared SQL statements. Until patched, limit administrative access and review access logs for suspicious SQL patterns.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Email Subscribers by Icegram Express' or 'Icegram Express'. Note the installed version number.
    Affected if The plugin is installed and the version is below 5.9.17
  2. Check WordPress user roles
    Navigate to Users > All Users in the WordPress admin panel and review which users have Administrator role.
    Affected if Any user has Administrator role and the vulnerable plugin version is installed
  3. Inspect plugin AJAX endpoints
    Check the plugin files (typically in wp-content/plugins/email-subscribers/) for AJAX handlers that process the 'workflow_ids' parameter, particularly in files handling workflow or export functionality.
    Affected if The plugin contains code processing workflow_ids without prepared statements (look for direct $wpdb->query or $wpdb->prepare missing)
  4. Review access logs for suspicious requests
    Examine web server access logs (Apache/Nginx) for POST requests to /wp-admin/admin-ajax.php with workflow_ids parameter containing unusual characters like quotes or SQL keywords.
    Affected if Any AJAX requests with workflow_ids contain SQL injection patterns

A user is affected if the Email Subscribers by Icegram Express plugin is installed with a version below 5.9.17 and has at least one administrator account.

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 version 5.9.17 or later which contains proper input sanitization and uses prepared SQL statements. Until patched, limit administrative access and review access logs for suspicious SQL patterns.

Recommended fix Moderate confidence

Version 5.9.17 or latest available version (check wordpress.org for current release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Email Subscribers by Icegram Express' (or 'Email Subscribers by Icegram')
  4. Check the current version - if it is 5.9.16 or below, an update is needed
  5. Update the plugin to the latest available version via WordPress plugin updates, or download from wordpress.org/plugins/email-subscribers/ and upload manually
  6. After updating, verify the workflow_ids parameter is properly sanitized in any custom code using this functionality
  7. Confirm the update completed successfully
Caveat Review plugin settings after upgrade as minor configuration changes may occur

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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