Skip to main content
Menu
CVEs

Metagauss ProfileGrid SQL injection in input handling exposes database data

Affects the WordPress ProfileGrid plugin by Metagauss, version 6.0.0.6 and earlier. Fixed in 6.0.0.7.

CVE-2026-131705Published , updated

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 6.0.0.7
Who is exposed
Specific setups only

Summary

The Metagauss ProfileGrid WordPress plugin has an SQL injection flaw that lets an attacker over the network, with a low-privilege account, run database commands through its input handling. The flaw can expose sensitive data from the site's database.

Written by a model

Original description

Improper 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 6.0.0.6.

Who should check

Sites and teams running the WordPress ProfileGrid plugin (profilegrid-user-profiles-groups-and-communities) version 6.0.0.6 or earlier.

“WordPress ProfileGrid Plugin <= 6.0.0.6”

patchstack.com

What to do

  1. Check whether your setup matches what the bug needs.

    ProfileGrid plugin version 6.0.0.6 or earlier
  2. Upgrade to a fixed version: 6.0.0.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131705 (WordPress ProfileGrid plugin <= 6.0.0.6 - SQL Injection vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131705 (entry last updated 2026-11-22):
Affected:
- Metagauss ProfileGrid: fixed in 6.0.0.7
Fixed versions: 6.0.0.7.
Conditions (all must be true for the bug to be hit):
- ProfileGrid plugin version 6.0.0.6 or earlier (source: https://patchstack.com/database/wordpress/plugin/profilegrid-user-profiles-groups-and-communities/vulnerability/wordpress-profilegrid-plugin-6-0-0-6-sql-injection-vulnerability-2?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131705 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131705 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/profilegrid-user-profiles-groups-and-communities/vulnerability/wordpress-profilegrid-plugin-6-0-0-6-sql-injection-vulnerability-2?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-131705
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131705
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131705"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

Questions about CVE-2026-131705

Is CVE-2026-131705 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A SQL injection flaw in the ProfileGrid plugin lets attackers read, modify, or delete the entire database, including user accounts and private data.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-131705?

profilegrid-user-profiles-groups-and-communities: through 6.0.0.6 (fixed in 6.0.0.7).

Source: cve.now feed data

Am I affected, and how do I check?

ProfileGrid plugin version 6.0.0.6 and earlier are affected. To check the installed version, look at the plugin's version shown on the WordPress Plugins page.

Source: patchstack.com, cve.org

How do I fix CVE-2026-131705?

Update the ProfileGrid plugin to version 6.0.0.7 or later, which is the fixed version.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.