dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-31291

HIGH · 7.1 CVSS v3.1 Published 2024-04-07
Fix available
A fix is available. Upgrade to 5.7.7 or later.
See remediation →
77/100
Remediation priority · High
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.6.

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 Through User-Controlled Key vulnerability in ProfileGrid, a WordPress user profile plugin. The vulnerability allows an attacker to manipulate a key parameter (such as a user ID or object reference) in API requests to bypass authorization checks and access or modify data belonging to other users or administrative functions that should be restricted.

MitigationUpgrade ProfileGrid to version 5.7.7 or later. If immediate patching is not possible, restrict access to the affected plugin endpoints via web server configuration or disable the plugin until the update can be applied.

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.7.7

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
Low
Availability
None

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

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 version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate ProfileGrid by Metagauss, and note the displayed version number. Alternatively, check the main plugin file (e.g., /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/profilegrid.php) for the 'Version' header comment.
    Affected if The installed version is below 5.7.7 (e.g., 5.7.6, 5.7.5, 5.0.0, etc.)
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that ProfileGrid is currently activated. Alternatively, query the WordPress options table for the active_plugins option to check if profilegrid is present.
    Affected if ProfileGrid is installed AND active with a version below 5.7.7
  3. Inspect API endpoint accessibility
    Identify ProfileGrid REST API endpoints by reviewing plugin files for registered REST routes (typically in the plugin initialization code registering endpoints under /wp-json/profilegrid/). Use a tool like curl or browser DevTools to send a test request to suspected API endpoints.
    Affected if ProfileGrid REST API endpoints are accessible and respond to requests without proper authorization validation on key parameters (user ID or object reference)
  4. Review access logs for suspicious API activity
    Examine web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for API calls to ProfileGrid endpoints where the user ID or object reference parameter differs from the authenticated user's actual ID, indicating potential parameter manipulation.
    Affected if Logs show API requests with user-controlled key parameters that access or modify data belonging to different users than the authenticated requester

Your environment is affected if ProfileGrid by Metagauss is active with a version lower than 5.7.7 and the plugin's API endpoints allow manipulation of key parameters to bypass authorization checks.

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.7.7 or later
Fixed in 5.7.7
Interim mitigation

Upgrade ProfileGrid to version 5.7.7 or later. If immediate patching is not possible, restrict access to the affected plugin endpoints via web server configuration or disable the plugin until the update can be applied.

Recommended fix High confidence

Profilegrid 5.7.7

  1. Backup your WordPress site database and files
  2. Update Profilegrid plugin to version 5.7.7 or later
  3. Verify the update was successful by checking the plugin version in WordPress admin
  4. Test that user authorization behaves correctly, particularly around user-controlled key operations
  5. Clear any caching layers if applicable

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

Fix this in Profilegrid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31291 — 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-31291 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