dbcve.org
ProfilegridWordPress extension · Metagauss

CVE-2025-0723

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-22
Fix available
A fix is available. Upgrade to 5.9.4.8 or later.
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 and time-based SQL Injections via the rid and search parameters in all versions up to, and including, 5.9.4.7 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.4.7 contain SQL injection vulnerabilities in the rid and search parameters. Authenticated attackers with Subscriber-level access can inject arbitrary SQL queries due to insufficient input sanitization and lack of prepared statements in the underlying SQL queries.

MitigationUpdate the ProfileGrid plugin to version 5.9.4.8 or later. Until then, restrict subscriber-level account creation and monitor for suspicious database query patterns.

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

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 version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > ProfileGrid. Check the version number displayed under the plugin name.
    Affected if The version shown is lower than 5.9.4.8 (e.g., 5.9.4.7, 5.9.4.6, etc.)
  2. Confirm subscriber role is active
    Go to WordPress admin > Users > Roles or ProfileGrid settings. Verify if the Subscriber role is enabled or if new user registration is allowed with Subscriber-level access.
    Affected if Subscriber role exists and is assignable to newly registered users, or any low-privilege role can be created via registration.
  3. Inspect plugin file for vulnerable parameters
    Access the WordPress file system via FTP or file manager. Locate the ProfileGrid plugin directory (wp-content/plugins/profilegrid-user-profiles-groups-and-communities). Search the main plugin files for code handling the 'rid' and 'search' GET/POST parameters, specifically looking for direct SQL queries without prepare() calls.
    Affected if Code contains SQL queries using $_REQUEST, $_GET, or $_POST['rid'] or $_REQUEST['search'] without $wpdb->prepare() or equivalent sanitization.
  4. Review database query logs
    Enable WordPress debug logging (wp-config.php: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true );). Examine wp-content/debug.log or database slow query logs for unusual SQL patterns containing UNION SELECT, OR 1=1, or similar SQL injection payloads.
    Affected if Log entries show suspicious SQL queries containing SQL injection payloads submitted through rid or search parameters.

You are affected if the ProfileGrid plugin version is below 5.9.4.8 AND subscriber-level accounts can be created or already exist in your WordPress environment.

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.9.4.8 or later
Fixed in 5.9.4.8
Interim mitigation

Update the ProfileGrid plugin to version 5.9.4.8 or later. Until then, restrict subscriber-level account creation and monitor for suspicious database query patterns.

Recommended fix High confidence

ProfileGrid 5.9.4.8

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find ProfileGrid – User Profiles, Groups and Communities in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 5.9.4.8 or later
  5. Alternatively, use WP-CLI: wp plugin update profilegrid
  6. Verify the plugin version is now 5.9.4.8 or higher after updating

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

Fix this in Profilegrid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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