CVE-2023-52119

Icegram <= 3.1.18 - Cross-Site Request Forgery via save_campaign_preview

2023-12-28 00:00
Brandon James Roldan (tomorrowisnew)

Strategic Overview

Status
Patched in 3.1.19
Affected Plugin
Icegram Engage – Popups, Optins, CTAs & Lead Generation
Affected Version
<= 3.1.18
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-52119
View all Icegram Engage – Popups, Optins, CTAs & Lead Generation vulnerabilities

At a glance

CVE-2023-52119 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Icegram Engage WordPress plugin, affecting versions <= 3.1.18. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.19; sites on affected versions should update now. Disclosed December 2023, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The Icegram plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.18. This is due to missing or incorrect nonce validation on the save_campaign_preview() function. This makes it possible for unauthenticated attackers to save campaign previews via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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-352: Cross-Site Request Forgery (CSRF)

Icegram Engage <= 3.1.18 carries this weakness at save_campaign_preview(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Icegram Engage the fix is 3.1.19: builds <= 3.1.18 are affected, anything from 3.1.19 onward is not.

Remediation

Update to version 3.1.19, 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 3.1.19 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-52119https://www.wordfence.com/threat-intel/vulnerabilities/id/3000b140-2e38-463d-9128-b486293e3cf6https://nvd.nist.gov/vuln/detail/CVE-2023-52119

Related records

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