CVE-2021-24922

Pixel Cat – Conversion Pixel Manager <= 2.6.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2021-11-15 00:00
ZhongFu Su

Strategic Overview

Status
Patched in 2.6.2
Affected Version
<= 2.6.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24922
View all Pixel Cat – Conversion Pixel Manager vulnerabilities

At a glance

CVE-2021-24922 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Pixel Cat WordPress plugin, affecting versions <= 2.6.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.6.2; sites on affected versions should update now. Disclosed November 2021, reported by ZhongFu Su.

Vulnerability Overview

The Pixel Cat – Conversion Pixel Manager WordPress plugin before 2.6.2 does not have CSRF check when saving its settings, and did not sanitise as well as escape some of them, which could allow attacker to make a logged in admin change them and perform 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Pixel Cat <= 2.6.1 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 Pixel Cat the fix is 2.6.2: builds <= 2.6.1 are affected, anything from 2.6.2 onward is not.

Remediation

Update to version 2.6.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Pixel Cat: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Pixel Cat 2.6.2 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