Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13416: CWE-862 Missing Authorization in metagauss ProfileGrid – User Profiles, Groups and Communities

0
Medium
VulnerabilityCVE-2025-13416cvecve-2025-13416cwe-862
Published: Thu Feb 05 2026 (02/05/2026, 08:25:43 UTC)
Source: CVE Database V5
Vendor/Project: metagauss
Product: ProfileGrid – User Profiles, Groups and Communities

Description

The ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to unauthorized user suspension due to a missing capability check on the pm_deactivate_user_from_group() function in all versions up to, and including, 5.9.7.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to suspend arbitrary users from groups, including administrators, via the pm_deactivate_user_from_group AJAX action.

AI-Powered Analysis

AILast updated: 02/05/2026, 08:59:43 UTC

Technical Analysis

CVE-2025-13416 is a vulnerability classified under CWE-862 (Missing Authorization) affecting the ProfileGrid – User Profiles, Groups and Communities plugin for WordPress, versions up to and including 5.9.7.2. The vulnerability arises from the absence of a proper capability check in the pm_deactivate_user_from_group() function, which is responsible for suspending users from groups. This function is accessible via an AJAX action named pm_deactivate_user_from_group. Because the plugin fails to verify whether the authenticated user has the necessary permissions to perform this action, any user with Subscriber-level access or higher can invoke this AJAX endpoint to suspend arbitrary users from groups, including administrators. This unauthorized suspension can disrupt group membership and administrative controls within WordPress sites using this plugin. The vulnerability has a CVSS 3.1 base score of 4.3, indicating medium severity, with an attack vector of network, low attack complexity, requiring low privileges (authenticated user), no user interaction, and unchanged scope. The impact is limited to integrity, as confidentiality and availability are not affected. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and should be addressed promptly to prevent misuse.

Potential Impact

For European organizations, the primary impact of this vulnerability is the potential disruption of group and community management within WordPress sites using the ProfileGrid plugin. Unauthorized suspension of users, including administrators, can lead to loss of administrative control, hinder collaboration, and cause operational disruptions in environments relying on group-based access or communication. While the vulnerability does not directly expose sensitive data or cause denial of service, the integrity compromise can facilitate further attacks or internal conflicts by disabling key user accounts. Organizations with public-facing or internally critical WordPress sites that utilize this plugin are at risk of privilege abuse by low-privilege authenticated users, potentially including malicious insiders or compromised accounts. This risk is heightened in sectors with collaborative platforms such as education, government, and enterprises that depend on WordPress for community management.

Mitigation Recommendations

1. Immediately audit user roles and permissions to ensure that only trusted users have Subscriber-level or higher access, minimizing the pool of potential attackers. 2. Temporarily disable or restrict the ProfileGrid plugin if feasible until an official patch is released. 3. Implement custom code or use security plugins to enforce capability checks on the pm_deactivate_user_from_group AJAX action, effectively adding authorization validation. 4. Monitor WordPress logs and AJAX requests for suspicious activity related to user suspension actions. 5. Educate administrators and users about the risk and encourage strong authentication practices to reduce account compromise likelihood. 6. Stay updated with vendor announcements and apply patches promptly once available. 7. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block unauthorized AJAX calls targeting this function. 8. Review and harden WordPress security configurations, including limiting plugin access and employing least privilege principles.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-19T14:44:44.565Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69845894f9fa50a62f0ebbde

Added to database: 2/5/2026, 8:45:08 AM

Last enriched: 2/5/2026, 8:59:43 AM

Last updated: 2/5/2026, 10:58:21 AM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats