dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-31362

HIGH · 8.8 CVSS v3.1 Published 2024-04-12
Fix available
A fix is available. Upgrade to 5.7.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Metagauss ProfileGrid.This issue affects ProfileGrid : from n/a through 5.7.8.

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

Cross-Site Request Forgery (CSRF) vulnerability in the ProfileGrid WordPress plugin versions up to 5.7.8. The plugin fails to properly validate anti-CSRF tokens (nonces) on sensitive actions, allowing attackers to trick authenticated administrators into unknowingly executing unwanted operations such as modifying user profiles, changing plugin settings, or performing privileged actions.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all state-changing form actions and AJAX endpoints within ProfileGrid. Add nonce verification to the server-side handlers and consider implementing SameSite cookie attributes.

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

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'ProfileGrid' or 'Metagauss Profilegrid' in the list of active plugins.
    Affected if ProfileGrid plugin appears in the installed plugins list and is activated.
  2. Check installed ProfileGrid version
    In WordPress admin, go to Plugins > Installed Plugins. Find ProfileGrid and locate the version number displayed beneath the plugin name. Alternatively, check the plugin file header in /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/profile-magic.php for the 'Version' tag.
    Affected if The displayed version number is below 5.7.9 (for example: 5.7.8, 5.7.7, etc).
  3. Confirm version comparison result
    Compare your installed version number against the affected range: any version less than 5.7.9 is vulnerable. Version 5.7.9 and later include the fix.
    Affected if Your installed version is 5.7.8 or any earlier version number.
  4. Identify active administrative endpoints
    Review your WordPress site for ProfileGrid-related admin pages under the ProfileGrid menu in the left sidebar. These include user profile management, group settings, and plugin configuration pages.
    Affected if ProfileGrid admin menu items are accessible, indicating the plugin is processing sensitive administrative actions.

You are affected if ProfileGrid plugin is active and the installed version is any version lower than 5.7.9, as these versions lack proper anti-CSRF nonce validation on sensitive actions.

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.9 or later
Fixed in 5.7.9
Interim mitigation

Implement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all state-changing form actions and AJAX endpoints within ProfileGrid. Add nonce verification to the server-side handlers and consider implementing SameSite cookie attributes.

Recommended fix High confidence

ProfileGrid version 5.7.9

  1. Backup your WordPress site and database before making any changes
  2. Log in to 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.7.9
  6. Verify the plugin is updated to version 5.7.9 or later
  7. Test that the ProfileGrid functionality works 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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