dbcve.org
Icegram ExpressWordPress extension · Icegram

CVE-2024-5756

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 5.7.24 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
The Email Subscribers by Icegram Express – Email Marketing, Newsletters, Automation for WordPress & WooCommerce plugin for WordPress is vulnerable to time-based SQL Injection via the db parameter in all versions up to, and including, 5.7.23 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers 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 is vulnerable to unauthenticated SQL injection via the db parameter in versions up to 5.7.23. The vulnerability stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the existing SQL query, allowing attackers to inject arbitrary SQL commands to extract sensitive database information.

MitigationUpdate the plugin to version 5.7.24 or later which contains the fix for this SQL injection vulnerability.

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
Icegram ExpressWordPress extension
Affected:< 5.7.24

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. Check installed plugin version via WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Email Subscribers by Icegram Express' (or 'Icegram Express') and read the version number displayed below the plugin name.
    Affected if The displayed version is lower than 5.7.24
  2. Check installed plugin version via wp-cli
    Run the command: wp plugin list --name='icegram-express' --format=table or wp plugin list --name='email-subscribers' --format=table to retrieve version information.
    Affected if The version column shows a number less than 5.7.24
  3. Check plugin files directly
    Access the plugin directory via FTP or file manager. Navigate to /wp-content/plugins/icegram-express/ or /wp-content/plugins/email-subscribers/. Open the main plugin PHP file (usually icegram-express.php or email-subscribers.php) and locate the 'Version:' header in the plugin comment block.
    Affected if The Version header shows a number less than 5.7.24
  4. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the plugin status. If the plugin is not active, the vulnerability cannot be exploited.
    Affected if The plugin is active and version is below 5.7.24

If the Icegram Express (Email Subscribers) plugin is active and its version is below 5.7.24, the environment is affected by this unauthenticated SQL injection vulnerability.

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.7.24 or later
Fixed in 5.7.24
Interim mitigation

Update the plugin to version 5.7.24 or later which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

Icegram Express version 5.7.24 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Icegram Express (Email Subscribers by Icegram Express)
  4. Click 'Update Now' to install version 5.7.24 or later
  5. Verify the update completed successfully

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

Fix this in Icegram Express Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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