dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-4010

HIGH · 8.8 CVSS v3.1 Published 2024-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to a missing capability check on the handle_ajax_request function in all versions up to, and including, 5.7.19. This makes it possible for authenticated attackers, with subscriber-level access and above, to cause a loss of confidentiality, integrity, and availability, by performing multiple unauthorized actions. Some of these actions could also be leveraged to conduct PHP Object Injection and SQL Injection attacks.

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 has a missing capability check on the handle_ajax_request function in versions up to 5.7.19. This allows any authenticated user with subscriber-level access (the lowest privilege role) to execute unauthorized AJAX actions, leading to potential data exposure, modification, and loss. The vulnerability also enables PHP Object Injection and SQL Injection attacks through improper input handling.

MitigationUpdate the plugin to version 5.7.20 or later which implements proper capability checks on the ajax handler. Audit existing user accounts and check for indicators of compromise given the multiple attack vectors possible.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm plugin installation
    Locate the Email Subscribers by Icegram Express plugin in your WordPress installation. Check the plugins directory or view the installed plugins list in the WordPress admin dashboard under Plugins > Installed Plugins.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the Email Subscribers by Icegram Express entry. The version number is displayed below the plugin name. Alternatively, open the main plugin file (icegram-express/icegram-express.php) and locate the Version header in the plugin comments.
    Affected if The installed version is 5.7.19 or lower
  3. Verify subscriber role exists
    In WordPress admin, go to Users > Users List. Look for any users assigned the Subscriber role. Alternatively, navigate to Users > Roles and confirm the Subscriber role is defined.
    Affected if One or more users with the Subscriber role exist in the WordPress site
  4. Check ajax handler accessibility
    Review the plugin files for the handle_ajax_request function. Inspect the ajax-actions.php or similar ajax handling files within the plugin directory. Verify if capability checks are present before processing the request.
    Affected if The handle_ajax_request function lacks proper capability checks (nonces/permission verification)

You are affected if the Email Subscribers by Icegram Express plugin version is 5.7.19 or lower and any subscriber-level user account exists in your WordPress installation.

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.7.20 or later which implements proper capability checks on the ajax handler. Audit existing user accounts and check for indicators of compromise given the multiple attack vectors possible.

Recommended fix High confidence

5.7.20 or later (latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Email Subscribers by Icegram Express' plugin
  4. If current version is 5.7.19 or earlier, click 'Update Now' to upgrade to the latest version
  5. After update, verify the new version number in the plugins list

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 / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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