CVE-2022-1776

Icegram Engage <= 2.1.7 - Cross-Site Scripting

2022-05-30 00:00
Pritam Dash

Strategic Overview

Status
Patched in 2.1.8
Affected Plugin
Icegram Engage – Popups, Optins, CTAs & Lead Generation
Affected Version
< 2.1.8
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-1776
View all Icegram Engage – Popups, Optins, CTAs & Lead Generation vulnerabilities

At a glance

CVE-2022-1776 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Icegram Engage WordPress plugin, affecting versions < 2.1.8. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.8; sites on affected versions should update now. Disclosed May 2022, reported by Pritam Dash.

Vulnerability Overview

The Popups, Welcome Bar, Optins and Lead Generation Plugin WordPress plugin before 2.1.8 does not sanitize and escape some campaign parameters, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

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

Reaching this weakness in Icegram Engage < 2.1.8 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Icegram Engage the fix is 2.1.8: builds < 2.1.8 are affected, anything from 2.1.8 onward is not.

Remediation

Update to version 2.1.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Icegram Engage: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Icegram Engage 2.1.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-1776https://www.wordfence.com/threat-intel/vulnerabilities/id/e75b3cc3-5bd6-4af9-94bf-2c3b6270e1c5https://nvd.nist.gov/vuln/detail/CVE-2022-1776

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C