CVE-2024-32808

ProfileGrid – User Profiles, Memberships, Groups and Communities <= 5.7.9 - Insecure Direct Object Reference

2024-04-22 00:00
Kyle Sanchez

Strategic Overview

Status
Patched in 5.8.0
Affected Plugin
ProfileGrid – User Profiles, Groups and Communities
Affected Version
<= 5.7.9
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-32808
View all ProfileGrid – User Profiles, Groups and Communities vulnerabilities

At a glance

CVE-2024-32808 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ProfileGrid WordPress plugin, affecting versions <= 5.7.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 5.8.0; sites on affected versions should update now. Disclosed April 2024, reported by Kyle Sanchez.

Vulnerability Overview

The ProfileGrid – User Profiles, Memberships, Groups and Communities plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.7.9 due to missing validation on a user controlled key in the pg_show_msg_panel() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to view other's messages.

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-639: Authorization Bypass Through User-Controlled Key

ProfileGrid <= 5.7.9 carries this weakness at pg_show_msg_panel(), and reaching it takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For ProfileGrid the fix is 5.8.0: builds <= 5.7.9 are affected, anything from 5.8.0 onward is not.

Remediation

Update to version 5.8.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: ProfileGrid 5.8.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-32808https://www.wordfence.com/threat-intel/vulnerabilities/id/09b26b78-b587-42f6-a9e3-c2945e91d29ehttps://nvd.nist.gov/vuln/detail/CVE-2024-32808

Related records

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