Pending AnalysisCVE-2026-4607

CVE-2026-4607: Authorization Bypass in ProfileGrid WordPress Plugin

Platform

wordpress

Component

profilegrid-user-profiles-groups-and-communities

Fixed in

5.9.8.5

CVE-2026-4607 describes an authorization bypass vulnerability affecting the ProfileGrid WordPress plugin. An authenticated attacker, even with Subscriber-level access, can manipulate critical site-wide group settings, potentially leading to configuration drift and unexpected behavior. This vulnerability impacts versions 0.0.0 through 5.9.8.4, and a patch is available in version 5.9.8.5.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Impact and Attack Scenarios

The primary impact of this vulnerability lies in the ability of an attacker to modify ProfileGrid group settings without proper authorization. This includes altering the group menu order, list order, icon display, and field ordering. While not a direct data breach, unauthorized modification of these settings can disrupt site functionality, create confusion for administrators, and potentially lead to misconfiguration impacting user experience. An attacker could systematically alter group settings to hinder legitimate users or create a misleading site structure. The blast radius is limited to the ProfileGrid plugin's functionality within the WordPress site, but the impact on site administration and user experience can be significant.

Exploitation Context

CVE-2026-4607 was published on May 13, 2026. Its CVSS score is 4.3 (MEDIUM). As of this writing, there are no publicly known Proof-of-Concept (POC) exploits. The vulnerability is not currently listed on KEV or EPSS, suggesting a low to medium probability of active exploitation. Monitor security advisories and WordPress vulnerability databases for updates.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N4.3MEDIUMAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredLowAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityNoneRisk of sensitive data exposureIntegrityLowRisk of unauthorized data modificationAvailabilityNoneRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
Low — any valid user account is sufficient. Basic authenticated access required.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
None — no confidentiality impact. Attacker cannot read protected data.
Integrity
Low — attacker can modify some data with limited scope or impact.
Availability
None — no availability impact. Service remains fully operational.

Affected Software

Componentprofilegrid-user-profiles-groups-and-communities
Vendorwordfence
Minimum version0.0.0
Maximum version5.9.8.4
Fixed in5.9.8.5

Weakness Classification (CWE)

Timeline

  1. Published

Mitigation and Workarounds

The primary mitigation is to upgrade the ProfileGrid plugin to version 5.9.8.5 or later. If an immediate upgrade is not feasible due to compatibility concerns or testing requirements, consider implementing a temporary workaround by restricting access to the pmsetgrouporder, pmsetgroupitems, and pmsetfield_order AJAX actions to administrators only. This can be achieved through custom code or a WordPress security plugin. Monitor WordPress logs for suspicious activity related to these AJAX actions. After upgrading, confirm the fix by logging in as a Subscriber and attempting to modify group settings – the action should be denied.

How to fix

Update to version 5.9.8.5, or a newer patched version

Frequently asked questions

What is CVE-2026-4607 — Authorization Bypass in ProfileGrid WordPress Plugin?

CVE-2026-4607 is a medium severity vulnerability in the ProfileGrid WordPress plugin allowing authenticated users (Subscriber level and above) to modify site-wide group settings without proper authorization, impacting configuration and potentially user experience.

Am I affected by CVE-2026-4607 in ProfileGrid WordPress Plugin?

You are affected if your WordPress site uses the ProfileGrid plugin and is running version 5.9.8.4 or earlier. Upgrade to 5.9.8.5 to mitigate the risk.

How do I fix CVE-2026-4607 in ProfileGrid WordPress Plugin?

Upgrade the ProfileGrid plugin to version 5.9.8.5 or later. As a temporary workaround, restrict access to the vulnerable AJAX actions to administrators only.

Is CVE-2026-4607 being actively exploited?

As of the current assessment, CVE-2026-4607 is not known to be actively exploited, but continuous monitoring is recommended.

Where can I find the official ProfileGrid advisory for CVE-2026-4607?

Refer to the official ProfileGrid website and WordPress plugin repository for the latest advisory and update information regarding CVE-2026-4607.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Scan your WordPress project now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...