CVE-2025-49876
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Metagauss ProfileGrid profilegrid-user-profiles-groups-and-communities allows SQL Injection.This issue affects ProfileGrid : from n/a through <= 5.9.5.2.
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 confidenceSQL Injection vulnerability in the ProfileGrid WordPress plugin allows attackers to inject malicious SQL commands via unsanitized user input. The vulnerability exists in versions up to 5.9.5.2 and could allow unauthorized database access, data exfiltration, or manipulation.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ProfileGrid plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the profilegrid-user-profiles-groups-and-blogs folder, or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if ProfileGrid plugin is present and active on the WordPress site
-
Identify the installed ProfileGrid versionOpen the main plugin file (profilegrid-user-profiles-groups-and-blogs/profile-grid.php) and locate the Version header in the plugin comment block, or check the readme.txt fileAffected if The version displayed is 5.9.5.2 or any version lower than 5.9.5.2
-
Verify the plugin handles user profile inputCheck if the ProfileGrid user registration or profile editing feature is enabled in WordPress admin under ProfileGrid settings > Global Settings > User ProfilesAffected if User registration or profile creation is enabled and users can submit profile data
-
Confirm WordPress database user privilegesReview the database user credentials in wp-config.php (DB_USER) and verify the scope of privileges granted to the WordPress database accountAffected if The WordPress database user has broad privileges beyond SELECT, INSERT, UPDATE, DELETE (such as DROP, CREATE, or administrative rights)
A site is affected if ProfileGrid plugin is installed with version 5.9.5.2 or lower and user profile registration/edit functionality is enabled, allowing unsanitized user input to reach the database.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate ProfileGrid to the latest patched version when available. As an interim measure, deploy a WAF rule to filter SQL injection payloads and ensure the database user has minimal required privileges.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-49876 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49876 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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