Icegram ExpressWordPress extension · Icegram
CVE-2024-21748
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 · uneditedMissing Authorization vulnerability in Icegram.This issue affects Icegram: from n/a through 3.1.21.
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 confidenceA missing authorization vulnerability exists in the Icegram WordPress plugin affecting versions through 3.1.21. The vulnerability allows unauthorized users to access certain functions or data that should require proper authentication and privilege verification.
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
< 3.1.22CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Icegram plugin version in WordPressIn the WordPress admin dashboard, go to Plugins > Installed Plugins. Find 'Icegram Express' or 'Icegram' in the list and note the version number displayed beneath the plugin name.Affected if The displayed version is any version before 3.1.22 (for example, 3.1.21, 3.1.20, 3.0.x, etc.)
-
Verify the plugin file header for version confirmationAccess the plugin directory via FTP or file manager. Navigate to wp-content/plugins/icegram-express or icegram and open the main plugin file (usually icegram-express.php or similar). Look for the version comment header: 'Version: x.x.x'Affected if The version listed in the plugin header is below 3.1.22
-
Check for active API endpoints or public-facing featuresIcegram Express is a marketing automation plugin. Review if the plugin has any REST API routes or public-facing forms enabled. This vulnerability affects unauthenticated access, so any active Icegram features could potentially be impacted.Affected if The plugin is active and version is below 3.1.22
A user is affected if the installed Icegram Express plugin version is any version prior to 3.1.22, as the missing authorization vulnerability exists in all those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.22
Upgrade Icegram to version 3.1.22 or later to obtain the patched version. If immediate patching is not possible, disable the plugin until an update can be applied.
Icegram Express 3.1.22 or later
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find Icegram Express (may be listed as Icegram) in the plugin list
- If an update is available, click 'Update Now' to update to version 3.1.22 or later
- Alternatively, download version 3.1.22 or latest version from the WordPress plugin repository and upload manually
- Verify the plugin updated successfully by checking the installed version
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
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21748 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21748 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
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.
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