CVE-2022-0233

ProfileGrid – User Profiles, Memberships, Groups and Communities <= 4.7.4 - Stored Cross-Site Scripting via Profile

2022-01-18 00:00
Big Tiger

Strategic Overview

Status
Patched in 4.7.7
Affected Version
<= 4.7.4
CVSS
6.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-0233
View all ProfileGrid – User Profiles, Groups and Communities vulnerabilities

At a glance

CVE-2022-0233 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the ProfileGrid WordPress plugin, affecting versions <= 4.7.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 4.7.7; sites on affected versions should update now. Disclosed January 2022, reported by Big Tiger.

Vulnerability Overview

The ProfileGrid – User Profiles, Memberships, Groups and Communities WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient escaping via the pm_user_avatar and pm_cover_image parameters found in the ~/admin/class-profile-magic-admin.php file which allows attackers with authenticated user access, such as subscribers, to inject arbitrary web scripts into their profile, in versions up to and including 4.7.4.

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 interaction from a victim user.

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

Reaching this weakness in ProfileGrid <= 4.7.4 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 ProfileGrid the fix is 4.7.7: builds <= 4.7.4 are affected, anything from 4.7.7 onward is not.

Remediation

Update to version 4.7.7, or a newer patched version

How does WordSec protect against this?

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