ProfileGrid <= 5.7.2 - Authenticated (Subscriber+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 5.7.3
- Affected Plugin
- ProfileGrid – User Profiles, Groups and Communities
- Affected Version
<= 5.7.2- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-30513
At a glance
CVE-2024-30513 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ProfileGrid WordPress plugin, affecting versions <= 5.7.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.7.3; sites on affected versions should update now. Disclosed March 2024, reported by Van Lyubov.
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.2 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above to perform an unauthorized action.
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
Reaching this weakness in ProfileGrid <= 5.7.2 takes an account at Subscriber level or above. 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.7.3: builds <= 5.7.2 are affected, anything from 5.7.3 onward is not.
Remediation
Update to version 5.7.3, 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.7.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in ProfileGrid – User Profiles, Groups and Communities
- 10.0CVE-2024-30490: ProfileGrid <= 5.7.8 SQL Injection
CVE-2024-30490 - 9.9CVE-2024-30491: ProfileGrid <= 5.7.8 SQL Injection
CVE-2024-30491 - 9.8CVE-2026-57697: ProfileGrid Privilege Escalation
CVE-2026-57697 - 8.8CVE-2025-0724: ProfileGrid PHP Object Injection
CVE-2025-0724 - 8.8CVE-2025-26999: ProfileGrid <= 5.9.4.3 PHP Object Injection
CVE-2025-26999 - 8.8CVE-2024-6411: ProfileGrid Authorization Bypass
CVE-2024-6411 - 8.8CVE-2023-3713: ProfileGrid <= 5.5.1 Arbitrary Option Update
CVE-2023-3713 - 8.8CVE-2023-0940: ProfileGrid <= 5.3.0 Arbitrary Password Reset
CVE-2023-0940
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C