dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4608

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The ProfileGrid – User Profiles, Groups and Communities plugin for WordPress is vulnerable to blind SQL Injection via the 'rid' parameter in all versions up to, and including, 5.9.8.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

The ProfileGrid WordPress plugin versions up to 5.9.8.4 contain a blind SQL injection vulnerability via the 'rid' parameter. Insufficient input escaping combined with the lack of prepared statements in the SQL query allows authenticated attackers with Subscriber-level permissions to inject arbitrary SQL queries, potentially exfiltrating sensitive database contents.

MitigationUpdate the ProfileGrid plugin to version 5.9.8.5 or later. If an update is unavailable, disable the plugin or implement WAF rules to block SQL injection attempts targeting the 'rid' parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ProfileGrid'. Note the version number displayed below the plugin name.
    Affected if ProfileGrid plugin is installed and version is 5.9.8.4 or lower
  2. Check plugin version directly
    Inspect the plugin main file (typically /wp-content/plugins/profilegrid-user-profiles-groups-and-communities/profile-magic.php) or check the version in the plugin header via FTP/shell access.
    Affected if The version read from the plugin file is 5.9.8.4 or any version lower than 5.9.8.5
  3. Confirm WordPress user roles exist
    Navigate to Users > All Users in WordPress admin and check if any users with 'Subscriber' role exist, or query the wp_users and wp_usermeta tables directly.
    Affected if At least one user with Subscriber-level permissions exists in the system
  4. Identify exposed endpoints using rid parameter
    Review web server access logs for requests to ProfileGrid endpoints containing the 'rid' parameter (e.g., URLs with 'rid=' query string). Common paths include /?pm_ajax=1&ajax=1&action=grid&rid= patterns.
    Affected if HTTP requests to ProfileGrid endpoints with the 'rid' parameter are being logged, indicating the feature is active and accessible

You are affected if ProfileGrid plugin version is 5.9.8.4 or lower, subscriber-level users exist in WordPress, and the plugin's features utilizing the rid parameter are accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ProfileGrid plugin to version 5.9.8.5 or later. If an update is unavailable, disable the plugin or implement WAF rules to block SQL injection attempts targeting the 'rid' parameter.

Recommended fix Moderate confidence

Version 5.9.8.5 or later (check wordpress.org for current stable release)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'ProfileGrid – User Profiles, Groups and Communities' in the plugin list
  4. 4. Check the current installed version against 5.9.8.4
  5. 5. If the installed version is 5.9.8.4 or lower, click 'Update Now' if an update is available
  6. 6. If no update is available through the WordPress admin, manually download the latest version from wordpress.org/plugins/profilegrid-user-profiles-groups-and-communities/
  7. 7. Deactivate the plugin, delete the old version, then upload and activate the new version
  8. 8. Verify the update was successful by checking the plugin version in the installed plugins list
Caveat Review plugin settings and group configurations after upgrade as minor changes between versions are possible

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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