dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2024-49273

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to after 5.9.3 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Metagauss ProfileGrid profilegrid-user-profiles-groups-and-communities.This issue affects ProfileGrid : from n/a through <= 5.9.3.

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

Missing Authorization vulnerability in ProfileGrid WordPress plugin allows authenticated users to potentially access or modify user profiles, groups, or community data without proper permission checks. This broken access control issue could enable privilege escalation or unauthorized data disclosure within the WordPress site.

MitigationImplement proper capability checks and authorization validation for all user profile, group, and community-related actions to ensure users can only access resources they are permitted to interact with.

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

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 installation and version
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'ProfileGrid' or 'Metagauss ProfileGrid' and note the version number displayed. Alternatively, inspect the main plugin file at wp-content/plugins/profilegrid-user-profiles-groups-and-communities/profile-magic.php and look for the 'Version' header in the plugin comments.
    Affected if The installed version is 5.9.3 or lower, indicating the vulnerable version is in use.
  2. Confirm ProfileGrid plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the ProfileGrid plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and the version is <= 5.9.3, exposing the vulnerability.
  3. Identify user roles with ProfileGrid access
    Navigate to ProfileGrid > User Groups in the WordPress admin. Review the existing groups and the roles assigned to them. Check WordPress Users > All Users to see which user roles exist on the site.
    Affected if There are multiple user roles present (especially non-administrator roles) with ProfileGrid group membership, indicating potential attack surface for unauthorized access.
  4. Check for exposed ProfileGrid endpoints
    Review the site's REST API endpoints by accessing /wp-json/ and look for routes containing 'profilegrid' or 'pm' (ProfileMagic). Also check wp-content/plugins/ for the profilegrid-user-profiles-groups-and-communities folder and its subdirectories.
  5. Audit existing user profile data accessibility
    Log in as a low-privileged user (subscriber or other non-admin role) if available on the site. Attempt to access ProfileGrid user profiles, groups, or community features directly via URL or by modifying ID parameters in ProfileGrid endpoints.
    Affected if A lower-privileged authenticated user can view, modify, or delete profiles, groups, or community data belonging to other users or higher-privileged roles without receiving a permission denied error.

The environment is affected if ProfileGrid version 5.9.3 or lower is installed and active with multiple user roles present, particularly if lower-privileged users can access or modify profile/group data without proper 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 a release after 5.9.3
Interim mitigation

Implement proper capability checks and authorization validation for all user profile, group, and community-related actions to ensure users can only access resources they are permitted to interact with.

Recommended fix Moderate confidence

Latest available version (5.9.4 or higher if available)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate ProfileGrid (profilegrid-user-profiles-groups-and-communities)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly on your site
  6. 6. Test that user authorization controls are working as expected

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

Fix this in Profilegrid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,700
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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