dbcve.org
Icegram EngageWordPress extension · Icegram

CVE-2023-52119

HIGH · 8.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to after 3.1.18 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Icegram Icegram Engage – WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building.This issue affects Icegram Engage – WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building: from n/a through 3.1.18.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Icegram Engage WordPress plugin versions up to 3.1.18 allows attackers to potentially trick authenticated administrators into performing unintended actions such as modifying plugin settings or creating malicious popups/optins.

MitigationUpdate to the latest version of Icegram Engage when a patch is released. In the interim, enable web application firewall rules to detect and block CSRF attempts.

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 EngageWordPress extension
Affected:<= 3.1.18

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Icegram Engage plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Icegram Engage' or 'Icegram'. Alternatively, check the /wp-content/plugins/ directory for the icegram-engage folder.
    Affected if The icegram-engage folder exists in the plugins directory
  2. Identify the installed version
    In WordPress admin > Plugins > Installed Plugins, find Icegram Engage and view the version number displayed under the plugin name. Alternatively, check the main plugin file (e.g., icegram-engage/icegram.php) for the 'Version' header comment.
    Affected if The displayed version is 3.1.18 or lower
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if Icegram Engage shows as 'Active' rather than 'Inactive' or 'Network Active'.
    Affected if The plugin status shows as Active and the version is 3.1.18 or lower
  4. Inspect plugin settings for unauthorized changes
    Navigate to Icegram Engage settings (usually under the Icegram menu in admin sidebar). Review all configuration options including campaign settings, email integrations, and display rules to detect any unexpected modifications.
    Affected if Settings have been changed without administrator intent, especially new API keys, modified redirect URLs, or altered campaign configurations
  5. Audit existing popups and optins for malicious content
    Go to Icegram > Campaigns or Popups/Optins section in the WordPress admin. Review all created campaigns for suspicious content, unintended redirects, or malicious links.
    Affected if New popups or optins exist that were not created by an authorized administrator

A user is affected if Icegram Engage version 3.1.18 or lower is installed and active on their WordPress site, particularly if unexpected plugin settings or campaigns are observed.

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.

From vendor data
Upgrade available Upgrade to a release after 3.1.18
Interim mitigation

Update to the latest version of Icegram Engage when a patch is released. In the interim, enable web application firewall rules to detect and block CSRF attempts.

Fix this in Icegram Engage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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