dbcve.org
Icegram EngageWordPress extension · Icegram

CVE-2021-36832

MEDIUM · 5.4 CVSS v3.1 Published 2021-10-19
Fix available
A fix is available. Upgrade to after 2.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
WordPress Popups, Welcome Bar, Optins and Lead Generation Plugin – Icegram (versions <= 2.0.2) vulnerable at "Headline" (&message_data[16][headline]) input.

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

Stored Cross-Site Scripting (XSS) vulnerability in the Icegram WordPress plugin (versions <= 2.0.2). The 'Headline' field (message_data[16][headline]) does not properly sanitize user input, allowing malicious scripts to be stored and executed when administrators or users view the affected popup/content.

MitigationUpdate Icegram plugin to version 2.0.3 or later which contains the patched version. If immediate update is not possible, disable the plugin until patched version can be deployed.

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:<= 2.0.2

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 Icegram plugin installation
    Check your WordPress installation for the Icegram Engage plugin in wp-content/plugins/ directory, or view it in the WordPress admin under Plugins > Installed Plugins
    Affected if The Icegram Engage plugin is present on the WordPress site
  2. Identify the installed Icegram version
    In WordPress admin, go to Plugins > Installed Plugins and find Icegram Engage. The version number is displayed below the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/icegram/engage/engage.php for the 'Version' header
    Affected if The displayed version is 2.0.2 or lower
  3. Review active popup or message campaigns
    In WordPress admin, navigate to Icegram Engage > Campaigns or Messages to list all created popups and message campaigns. Check if any campaigns contain a 'Headline' field in their configuration
    Affected if There are active campaigns with a Headline field configured, and the plugin version is 2.0.2 or lower
  4. Inspect the Headline field storage in the database
    Access the WordPress database via phpMyAdmin or command line. Query the wp_postmeta table for postmeta_key containing 'headline' (e.g., SELECT * FROM wp_postmeta WHERE meta_key LIKE '%headline%'). Examine the meta_value field for unescaped HTML or script tags
    Affected if The Headline field values contain raw HTML script tags or unescaped special characters like <script>, javascript:, or event handlers

You are affected if Icegram Engage plugin version 2.0.2 or lower is installed AND there are campaigns or messages with a Headline field that may contain unsanitized user-supplied content.

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 a release after 2.0.2
Interim mitigation

Update Icegram plugin to version 2.0.3 or later which contains the patched version. If immediate update is not possible, disable the plugin until patched version can be deployed.

Recommended fix Moderate confidence

2.0.3 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate the Icegram Engage plugin
  4. Update the plugin to the latest available version (version 2.0.3 or higher)
  5. Verify the update was successful by checking the installed plugin version

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

Fix this in Icegram Engage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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