dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49033

HIGH · 8.5 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 profilegrid-user-profiles-groups-and-communities allows Blind SQL Injection.This issue affects ProfileGrid : from n/a through <= 5.9.5.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 · high confidence

A blind SQL injection vulnerability exists in the ProfileGrid WordPress plugin (versions up to 5.9.5.3) due to improper neutralization of special elements in SQL commands. Attackers can inject malicious SQL queries through unsanitized input parameters, potentially allowing unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpdate ProfileGrid to the latest patched version. If no patch is available, disable the plugin until a fix is released. Alternatively, implement proper input sanitization and convert all database queries to prepared statements/parameterized queries.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 check the /wp-content/plugins/ directory for the profilegrid folder
    Affected if ProfileGrid plugin is present in the WordPress installation
  2. Identify the installed ProfileGrid version
    Check the plugin version in the plugin header (main plugin file) or in WordPress admin under Plugins > Installed Plugins > ProfileGrid, or inspect the version constant in profilegrid.php
    Affected if The displayed version is 5.9.5.3 or any earlier version (any version up to and including 5.9.5.3)
  3. Confirm the plugin is active
    Check WordPress admin > Plugins > Installed Plugins to verify ProfileGrid status shows 'Active'
    Affected if ProfileGrid is currently activated on the site
  4. Identify exposed user input endpoints
    Review ProfileGrid settings and profile creation forms - any field accepting user input (such as profile fields, registration fields, or search parameters) that interacts with the database could be a potential injection point
    Affected if User-facing profile fields or input forms are enabled and accessible to unauthenticated or low-privilege users

You are affected if ProfileGrid plugin versions 5.9.5.3 or earlier are installed and active, with user input fields exposed that could be exploited for SQL injection.

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 ProfileGrid to the latest patched version. If no patch is available, disable the plugin until a fix is released. Alternatively, implement proper input sanitization and convert all database queries to prepared statements/parameterized queries.

Recommended fix Moderate confidence

5.9.6 or later (latest stable version available on WordPress.org)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate ProfileGrid (user profiles, groups and communities) in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version number matches the latest stable release.
  7. 7. Test critical user profile and group functionality to ensure the update did not break existing features.
Caveat Review the plugin changelog for any breaking changes between your current version and the latest release; test in a staging environment first

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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