CVE-2021-24330

Funnel Builder by CartFlows <= 1.6.12 - Authenticated Stored Cross-Site scripting via FB Pixel ID and Google Analytics ID

2021-05-17 00:00
R3N0

Strategic Overview

Status
Patched in 1.6.13
Affected Version
< 1.6.13
CVSS
4.8Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24330
View all CartFlows – Funnel Builder & Checkout Plugin for WooCommerce vulnerabilities

At a glance

CVE-2021-24330 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the CartFlows WordPress plugin, affecting versions < 1.6.13. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.6.13; sites on affected versions should update now. Disclosed May 2021, reported by R3N0.

Vulnerability Overview

The Funnel Builder by CartFlows – Create High Converting Sales Funnels For WordPress plugin before 1.6.13 did not sanitise its facebook_pixel_id and google_analytics_id settings, allowing high privilege users to set XSS payload in them, which will either be executed on pages generated by the plugin, or the whole website depending on the settings used.

Technical Analysis

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

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

Reaching this weakness in CartFlows < 1.6.13 takes any authenticated account. 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 CartFlows the fix is 1.6.13: builds < 1.6.13 are affected, anything from 1.6.13 onward is not.

Remediation

Update to version 1.6.13, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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