LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36832: WordPress Icegram plugin <= 2.0.2 - Authenticated Stored Cross-Site Scripting (XSS) vulnerability

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

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-36832 is a stored cross-site scripting flaw in the WordPress Icegram plugin through version 2.0.2. A privileged authenticated user could store unsafe content in the Headline field, which may run in another user's browser when viewed.

Executive priority

Treat as a moderate-priority WordPress plugin issue. It is not identified as actively exploited in the provided evidence, but affected sites should be remediated during normal security maintenance because stored XSS can affect trusted administrator workflows.

Technical view

The issue is CWE-79 in Icegram's Headline input, identified as message_data[16][headline]. CVSS 3.1 is 4.8, with network access, low attack complexity, high privileges required, user interaction required, changed scope, and limited confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites running Icegram versions 2.0.2 or earlier, especially where multiple privileged users can create or edit Icegram messages, popups, bars, opt-ins, or lead-generation content.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires authenticated high privileges and another user interacting with affected stored content, reducing broad internet-scale urgency but still relevant for administrator-session risk.

Researcher notes

Focus validation on authenticated content-editing paths for Icegram Headline data. The bundle identifies the vulnerable parameter and affected version boundary, but does not provide exploit evidence or a named fixed version, so remediation should follow vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Icegram plugin and recorded versions.
  • Prioritize remediation for Icegram versions 2.0.2 or earlier.
  • Check WordPress and Patchstack vendor guidance for the fixed or recommended release.
  • Disable or remove vulnerable Icegram deployments if no approved update is available.
  • Limit plugin content-editing rights to trusted administrators only.
  • Review plugin-created Headline content for unexpected script-like markup.

Validation and detection

  • Confirm whether Icegram is installed on each WordPress property.
  • Record the installed Icegram version and compare it with <= 2.0.2.
  • Identify users or roles allowed to edit Icegram content.
  • Review affected Headline fields for suspicious stored HTML or script-like content.
  • After remediation, verify the site no longer runs an affected version.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-36832 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.8Medium
CVSS 3.1 vector shape for CVE-2021-36832Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IcegramPopups, Welcome Bar, Optins and Lead Generation Plugin – Icegram<= 2.0.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.