dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2023-52117

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to 5.6.7 or later.
See remediation →
69/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Metagauss ProfileGrid.This issue affects ProfileGrid: from n/a through 5.6.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

Missing Authorization vulnerability in ProfileGrid WordPress plugin up to version 5.6.6 allows unauthorized users to access or modify data they should not have permissions for due to missing capability checks or access control validation on certain functionality.

MitigationUpdate ProfileGrid to the latest version (5.6.7 or later) which contains the patched authorization checks, or manually add proper capability checks and nonce verification to the affected plugin functions.

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.6.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
Low
Integrity
Low
Availability
Low

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

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, go to Plugins > Installed Plugins and look for 'ProfileGrid' or 'Metagauss Profilegrid' in the list of active plugins.
    Affected if ProfileGrid is installed and active
  2. Check installed ProfileGrid version
    In WordPress admin, go to Plugins > Installed Plugins, find ProfileGrid, and note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/profilegrid.php for the 'Version' field.
    Affected if Version is 5.6.6 or lower (anything less than 5.6.7)
  3. Identify exposed ProfileGrid endpoints or AJAX actions
    Review source code in /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/ for PHP functions handling user profile operations, group management, or frontend submissions. Check for AJAX action hooks (add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...')) that handle sensitive operations.
    Affected if Sensitive AJAX actions are accessible to unauthenticated or unauthorized users (wp_ajax_nopriv_ handlers without capability checks)
  4. Inspect plugin functions for capability checks
    Examine the PHP functions identified as handling user data or group modifications. Search for current_user_can(), check_admin_referer(), or wp_verify_nonce() calls within these functions.
    Affected if Functions handling user data or group operations lack proper capability checks or nonce verification

Your environment is affected if ProfileGrid version is 5.6.6 or lower and the plugin exposes user-related functionality 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 5.6.7 or later
Fixed in 5.6.7
Interim mitigation

Update ProfileGrid to the latest version (5.6.7 or later) which contains the patched authorization checks, or manually add proper capability checks and nonce verification to the affected plugin functions.

Recommended fix Moderate confidence

ProfileGrid 5.6.7

  1. 1. Create a complete backup of your WordPress site, including both files and database, before making any changes.
  2. 2. Log in to your WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Locate ProfileGrid in the plugin list.
  5. 5. If an update to version 5.6.7 is available, click the 'Update Now' button to update ProfileGrid to the patched version.
  6. 6. After the update completes, verify the installed version shows 5.6.7.
  7. 7. Test user registration, profile management, and group functionality to ensure the update did not break legitimate functionality.
Caveat Review the ProfileGrid changelog for version 5.6.7 to check for any feature changes that may affect your site's user workflows

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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