Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain low-privilege account
-
DeliverySend crafted request to vulnerable ProfileGrid parameter
-
ExploitInject blind SQL into backend query
-
ExecutionInfer data via boolean/time-based responses
-
ImpactExfiltrate credentials and sensitive database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the ProfileGrid plugin (versions through 6.0.0.2) installed and active on a WordPress site, and a low-privilege authenticated session (CVSS PR:L) - typically satisfied because ProfileGrid is a user-profile/community plugin that commonly permits self-registration, lowering the authentication barrier. No user interaction is needed (UI:N) and the attack is network-reachable (AV:N) with low complexity (AC:L). The exact vulnerable feature/endpoint and parameter are not specified in the available data, so defenders cannot pin the trigger to a named setting; the primary limiting factor is the need for at least minimal authenticated access and the plugin being present, meaning sites that disable open registration materially raise the bar for attackers. |
| Impact | This is a CWE-89 blind SQL injection in the Metagauss ProfileGrid WordPress plugin, reported by Patchstack with a CVSS 3.1 base score of 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L). The vector signals a network-reachable, low-complexity attack requiring low privileges (PR:L) and no user interaction, with a changed scope and high confidentiality impact - consistent with an authenticated user (e.g., a registered community member/subscriber) extracting data from the WordPress database. No EPSS score, CISA KEV entry, SSVC decision data, or public POC was supplied in the input, so there is no evidence of active exploitation: this should currently be treated as no public exploit identified at time of analysis. The practical risk is driven by the low privilege bar - ProfileGrid is a community/registration plugin whose entire purpose is to let users self-register, so PR:L is often trivially satisfied, raising real-world risk above what the 'authenticated' label might suggest. The CVSS I:N/A:L combination fits blind SQLi (primarily read-oriented), but blind SQLi can often be escalated to fuller database disclosure; the S:C (scope change) assertion is plausible for a WordPress plugin that can reach the shared database but is not independently verifiable from the single reference. Net: a genuine high-priority patch item for sites running this plugin with open registration, not merely a high-CVSS-but-low-risk issue, though the absence of EPSS/KEV/POC means widespread automated exploitation is not yet demonstrated. |
| Exploit ScenarioDerived | An attacker registers (or uses an existing low-privilege) account on a WordPress site running ProfileGrid ≤ 6.0.0.2, then sends a crafted request to a vulnerable plugin endpoint whose parameter is concatenated into an SQL query. Because the flaw is blind, the attacker infers results via boolean/time-based responses to progressively dump sensitive data such as user credentials, session tokens, or other table contents. No public POC was provided in the input, and the low attack complexity (AC:L) with no user interaction (UI:N) makes the injection straightforward to automate once an authenticated session exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Blind SQL injection in the Metagauss ProfileGrid WordPress plugin (all versions through 6.0.0.2) lets an authenticated low-privilege user, such as a self-registered member of a community site, inject arbitrary SQL into a vulnerable plugin query and infer database contents through response timing or boolean differences. The issue is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N, reported base score 8.5), with the practical barrier lowered because ProfileGrid is a user-profile/community plugin that frequently permits open self-registration; the independent assessment rates confidentiality impact as High, integrity Low, availability None. No public exploit code and no confirmed active exploitation were identified at time of analysis. The specific vulnerable endpoint and parameter are not named in the available data, so defenders cannot pin the trigger to a specific setting.
RemediationAI
Vendor patch status is not confirmed in the available data: the advisory range extends "through 6.0.0.2" and no fixed release version is identified, so no vendor-released patch can be cited at this time - site owners should check the Patchstack record at https://patchstack.com/database/wordpress/plugin/profilegrid-user-profiles-groups-and-communities/vulnerability/wordpress-profilegrid-plugin-6-0-0-2-sql-injection-vulnerability?_s_id=cve and the Metagauss plugin page for a patched release before updating. Because the attack requires a low-privilege authenticated session, the most effective compensating control is to close the self-registration path that supplies it: disable open registration for the community, require administrator approval for new accounts, or restrict profile/community features to already-vetted users - the trade-off is reduced user onboarding and potentially broken member workflows. If ProfileGrid is not essential, deactivate and remove the plugin entirely, which eliminates the attack surface but drops all profile, group, and community functionality. Additionally, deploy WAF or virtual-patching rules that inspect requests to ProfileGrid endpoints for SQL metacharacters and boolean/time-based injection patterns; this blocks common payloads but can be bypassed with encoding tricks and may produce false positives on legitimate input. Finally, reduce blast radius by ensuring the WordPress database account used by the plugin has only the privileges it needs (no FILE, no cross-database access), enabling query logging or database activity monitoring to detect anomalous SELECT/UNION/SLEEP traffic, and rotating credentials and reviewing user accounts for unauthorized creations given that data disclosure cannot be ruled out on already-exposed sites.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a CWE-89 improper neutralization of special elements in an SQL command, i.e. classic SQL injection, in the PHP code of the ProfileGrid WordPress plugin (CPE cpe:2.3:a:metagauss:profilegrid:*:*:*:*:*:*:*:*). Plugin code builds a database query by concatenating user-controlled input rather than using WordPress's prepared-statement APIs ($wpdb->prepare), so an attacker can append SQL syntax that is parsed by the underlying MySQL/MariaDB backend. Because the injection is blind, the query results are not reflected directly in the page; the attacker instead infers data by observing conditional response differences (boolean-based) or induced delays (time-based), which makes exploitation slower and noisier but still capable of extracting user records, password hashes, and other data accessible to the WordPress database account. The CVSS vector's PR:L indicates the vulnerable code path is reachable only with at least a low-privilege authenticated session, which in a ProfileGrid deployment is commonly obtainable through the plugin's own self-registration flow; the vulnerability was reported by Patchstack.
Know when Profilegrid gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
Network-reachable blind SQLi exploitable by a low-privilege registered user (PR:L, AC:L); primarily database read (C:H) with limited write potential (I:L); scope assessed unchanged absent evidence of cross-component impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
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 6.0.0.2.
Executive ViewAI
Metagauss ProfileGrid, a WordPress community and user-profile plugin used on versions through 6.0.0.2, exposes organizations that allow member self-registration to a high-severity blind SQL injection. An authenticated low-privilege member can exploit this flaw to infer database contents, creating a realistic confidentiality risk to member, customer, or community data; no public exploit was identified at time of analysis, but open self-registration lowers the practical barrier to abuse. Leadership should prioritize containment because no vendor-released patch is currently available.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing the Metagauss ProfileGrid plugin if it is not required, temporarily disabling open self-registration and limiting low-privilege profile access, applying WAF or virtual-patching rules to block SQL injection against WordPress and ProfileGrid endpoints, enforcing least-privilege database permissions, monitoring for blind SQL injection timing or boolean anomalies, and migrating to an alternative community or profile plugin if no vendor fix becomes available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Profilegrid
View allImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Metagauss ProfileG
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Metagauss ProfileG
The ProfileGrid WordPress plugin before 5.3.1 provides an AJAX endpoint for resetting a user password but does not imple
The profilegrid-user-profiles-groups-and-communities plugin before 2.8.6 for WordPress has remote code execution via an
Privilege escalation in the ProfileGrid WordPress plugin before 5.9.9.8 lets unauthenticated visitors self-register into
Authentication bypass in ProfileGrid WordPress plugin allows unauthenticated attackers to forge PayPal IPN payment notif
The ProfileGrid WordPress plugin before 5.1.1 does not sanitise and escape a parameter before outputting it back in the
Missing authorization checks in ProfileGrid WordPress plugin prior to 5.9.9.7 allow authenticated subscribers to manipul
ProfileGrid WordPress plugin (all versions before 6.0.0.0) exposes group member lists and member identifiers to unauthen
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Metagauss ProfileG
The ProfileGrid - User Profiles, Groups and Communities plugin for WordPress is vulnerable to PHP Object Injection in al
The ProfileGrid - User Profiles, Groups and Communities plugin for WordPress is vulnerable to privilege escalation in al
EUVD-2026-95619
GHSA-8m54-mr8m-8q53
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB