dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-32772

HIGH · 8.8 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 5.8.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization Bypass Through User-Controlled Key vulnerability in Metagauss ProfileGrid.This issue affects ProfileGrid : from n/a through 5.7.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authorization bypass vulnerability in the ProfileGrid WordPress plugin where user-controlled input is used to determine access to sensitive functionality or data. Attackers can manipulate parameters (likely IDs or keys) to bypass authorization checks and access resources belonging to other users or administrative functions without proper permissions.

MitigationUpdate ProfileGrid to the latest version which contains proper authorization validation. If no update is available, implement additional server-side authorization checks on all sensitive endpoints and replace direct object references with indirect references.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ProfilegridWordPress extension
Affected:< 5.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify ProfileGrid plugin is installed
    Check for the presence of the ProfileGrid plugin directory at wp-content/plugins/profilegrid* or view the installed plugins list in WordPress admin under Plugins
    Affected if ProfileGrid plugin is found in the WordPress installation
  2. Determine installed ProfileGrid version
    Access the plugin file header (e.g., profilegrid.php) and read the 'Version' comment, or check the plugin version displayed in WordPress admin under Plugins > Installed Plugins
    Affected if The version string returned is lower than 5.8.0
  3. Confirm vulnerable endpoint accessibility
    Inspect network requests or logs for ProfileGrid-related AJAX actions or frontend endpoints that accept user IDs or keys as parameters (e.g., pm_ajax requests with user_id or group_id parameters)
    Affected if Requests to ProfileGrid endpoints accept raw user-controlled IDs without validated authorization checks

A user is affected if ProfileGrid plugin version is below 5.8.0 and the plugin is active with accessible endpoints that use user-controlled parameters for access control decisions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.8.0 or later
Fixed in 5.8.0
Interim mitigation

Update ProfileGrid to the latest version which contains proper authorization validation. If no update is available, implement additional server-side authorization checks on all sensitive endpoints and replace direct object references with indirect references.

Recommended fix High confidence

Profilegrid version 5.8.0 or later

  1. Create a complete backup of your WordPress site, including the database and all plugin files
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find ProfileGrid in the plugin list
  5. Click 'Update Now' if an update is available, or manually upload version 5.8.0 from the WordPress plugin repository
  6. Verify the plugin updated successfully to version 5.8.0 or later
  7. Test user profile functionality to confirm the plugin is working correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Profilegrid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32772 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data