dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-30241

HIGH · 8.8 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 5.7.2 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Metagauss ProfileGrid.This issue affects ProfileGrid : from n/a through 5.7.1.

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

SQL Injection vulnerability in Metagauss ProfileGrid plugin allows attackers to inject malicious SQL commands through unsanitized user input in database queries. The flaw exists in the plugin's handling of SQL queries, potentially allowing remote authenticated attackers to manipulate database operations.

MitigationUpgrade to ProfileGrid version 5.7.2 or later. If immediate patching is not possible, implement input validation and use parameterized queries for all database interactions.

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

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
    In WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'ProfileGrid' or 'Metagauss ProfileGrid' in the list of active plugins
    Affected if ProfileGrid plugin is present and active in the WordPress installation
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins, find ProfileGrid, and compare the version number displayed against the affected range (less than 5.7.2)
    Affected if Installed version is lower than 5.7.2
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and verify if 'Membership - Anyone can register' is enabled, or check ProfileGrid settings for user registration functionality
    Affected if User registration is enabled, allowing potential authenticated attackers to register
  4. Verify database query usage
    Review ProfileGrid plugin settings and any custom integrations that use the plugin's user data in database queries. Check if custom code or plugin features query the database using user-supplied input without proper sanitization
    Affected if Plugin features or custom code pass unsanitized user input directly to database queries

User is affected if ProfileGrid plugin versions below 5.7.2 are installed with user registration or authenticated user access enabled, and the plugin handles database queries with user-supplied input.

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.2 or later
Fixed in 5.7.2
Interim mitigation

Upgrade to ProfileGrid version 5.7.2 or later. If immediate patching is not possible, implement input validation and use parameterized queries for all database interactions.

Recommended fix High confidence

ProfileGrid version 5.7.2

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > All Plugins in your WordPress admin dashboard
  3. Find ProfileGrid in the plugin list
  4. Click 'Update now' on the ProfileGrid plugin or update it via WordPress updates
  5. Verify the plugin is running version 5.7.2 after the update
  6. Test critical user registration and profile functionality to ensure the plugin works correctly after the update
Caveat Review the plugin changelog before updating as minor version updates may include functionality changes

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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