Icegram EngageWordPress extension · Icegram
CVE-2023-51532
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Icegram Icegram Engage – WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building allows Stored XSS.This issue affects Icegram Engage – WordPress Lead Generation, Popup Builder, CTA, Optins and Email List Building: from n/a through 3.1.19.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Icegram Engage WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The malicious payload is stored in the database and executes when other users view affected pages in the plugin's popup, CTA, or opt-in forms.
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
<= 3.1.19CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Icegram Engage plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Icegram Engage' or 'Icegram Email Marketing' in the listAffected if Plugin is present in the plugins list
-
Check installed plugin versionIn the plugins list, click on the plugin name or view details to see the installed version number. Compare it to the affected range: version 3.1.19 or lowerAffected if Installed version is 3.1.19 or lower
-
Identify active popup, CTA, or opt-in form configurationsLook for Icegram menu items in the WordPress admin sidebar (such as Popups, CTAs, or Campaigns). Check if any of these features have active configurations or published formsAffected if The plugin has any published popups, CTAs, or opt-in forms that accept user input
-
Inspect form input fields for lack of sanitizationAccess any active Icegram popup or CTA settings and examine input fields (such as headline, message, button text, or custom fields) where content is stored and displayed to usersAffected if Input fields accept and store raw HTML or JavaScript without sanitization
A user is affected if the Icegram Engage plugin version is 3.1.19 or lower and any popups, CTAs, or opt-in forms are actively configured in the environment.
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.
From vendor dataUpdate Icegram Engage plugin to version 3.1.20 or later to receive the patched version that properly sanitizes user input. Review existing content for malicious payloads before updating.
Fix this in Icegram Engage
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51532 — 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-2023-51532 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