dbcve.org
Email Subscribers \& NewslettersWordPress extension · Icegram

CVE-2024-31352

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 5.7.14 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
Missing Authorization vulnerability in Email Subscribers & Newsletters.This issue affects Email Subscribers & Newsletters: from n/a through 5.7.13.

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 Missing Authorization vulnerability in the Email Subscribers & Newsletters WordPress plugin (versions through 5.7.13) allows unauthenticated attackers to access sensitive functionality or data that should require proper authorization checks. The CVSS 9.8 indicates this is exploitable over the network without authentication and can lead to unauthorized actions such as accessing subscriber data, modifying settings, or sending emails.

MitigationUpdate to the latest version of Email Subscribers & Newsletters plugin which includes proper authorization checks. If no patch is available, restrict access to the plugin's admin interfaces at the web server level or disable the plugin until a fix is released.

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
Email Subscribers \& NewslettersWordPress extension
Affected:< 5.7.14

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. Locate the plugin installation directory
    Check your WordPress wp-content/plugins/ folder for a folder named 'email-subscribers' or 'icegram-email-subscribers'. If using a managed WordPress host, you may need to access files via FTP or the hosting file manager.
    Affected if The plugin folder exists on the server
  2. Determine the installed plugin version
    Open the main plugin PHP file (typically email-subscribers/email-subscribers.php) and look for the 'Version' header comment in the file, or check the version via WordPress admin under Plugins > Installed Plugins.
    Affected if The version shown is lower than 5.7.14 (for example: 5.7.13, 5.7.12, etc.)
  3. Verify the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Check if 'Email Subscribers & Newsletters' by Icegram shows as 'Active'.
    Affected if The plugin is active and the version is below 5.7.14

You are affected if the Icegram Email Subscribers & Newsletters plugin is installed, active, and running a version lower than 5.7.14, as this allows unauthenticated network attackers to access sensitive subscriber data and plugin settings.

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.14 or later
Fixed in 5.7.14
Interim mitigation

Update to the latest version of Email Subscribers & Newsletters plugin which includes proper authorization checks. If no patch is available, restrict access to the plugin's admin interfaces at the web server level or disable the plugin until a fix is released.

Recommended fix High confidence

5.7.14

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. 3. Find 'Email Subscribers & Newsletters' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 5.7.14 or later
  5. 5. Alternatively, go to Dashboard > Updates to update all plugins including Email Subscribers & Newsletters
  6. 6. After updating, verify the plugin version shows 5.7.14 or higher in the Plugins list
  7. 7. Test that key functionality (sending emails, managing subscribers) continues to work correctly

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

Fix this in Email Subscribers \& Newsletters Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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