CVE-2024-10900

ProfileGrid – User Profiles, Groups and Communities <= 5.9.3.6 - Missing Authorization to Authenticated (Subscriber+) Arbitrary User Meta Deletion

2024-11-19 00:00
1337_Wannabe

Strategic Overview

Status
Patched in 5.9.3.7
Affected Version
<= 5.9.3.6
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10900
View all ProfileGrid – User Profiles, Groups and Communities vulnerabilities

At a glance

CVE-2024-10900 is a medium-severity Missing Authorization vulnerability in the ProfileGrid WordPress plugin, affecting versions <= 5.9.3.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.9.3.7; sites on affected versions should update now. Disclosed November 2024, reported by 1337_Wannabe.

Vulnerability Overview

The ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the pm_remove_file_attachment() function in all versions up to, and including, 5.9.3.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary user meta which can do things like deny an administrator's access to their site. .

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

ProfileGrid <= 5.9.3.6 carries this weakness at pm_remove_file_attachment(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For ProfileGrid the fix is 5.9.3.7: builds <= 5.9.3.6 are affected, anything from 5.9.3.7 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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