ProfileGrid <= 5.9.8.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Message Deletion
Strategic Overview
- Status
- Patched in 5.9.8.2
- Affected Plugin
- ProfileGrid – User Profiles, Groups and Communities
- Affected Version
<= 5.9.8.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-2488
At a glance
CVE-2026-2488 is a medium-severity Missing Authorization vulnerability in the ProfileGrid WordPress plugin, affecting versions <= 5.9.8.1. 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.9.8.2; sites on affected versions should update now. Disclosed March 2026, reported by Sergej Ljubojevic.
Vulnerability Overview
The ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to unauthorized message deletion due to a missing capability check on the pg_delete_msg() function in all versions up to, and including, 5.9.8.1. This is due to the function not verifying that the requesting user has permission to delete the targeted message. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary messages belonging to any user by sending a direct request with a valid message ID (mid parameter).
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-862: Missing Authorization
ProfileGrid <= 5.9.8.1 carries this weakness at pg_delete_msg(), 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.8.2: builds <= 5.9.8.1 are affected, anything from 5.9.8.2 onward is not.
Remediation
Update to version 5.9.8.2, 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.8.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 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 - 7.5CVE-2023-3714: ProfileGrid Arbitrary Group Option Modification
CVE-2023-3714 - 7.1CVE-2026-4609: ProfileGrid Authenticated (Subscriber+) Arbitrary
CVE-2026-4609
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 - 9.8CVE-2026-12073: ProfileGrid - User Profiles Privilege Escalation
CVE-2026-12073 - 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-2019-15873: ProfileGrid RCE
CVE-2019-15873
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C