Takeaway: On November 22, 2026, the U.S. National Vulnerability Database published four high-severity CVEs in ProfileGrid, the Metagauss WordPress plugin for user profiles, groups, and communities. The records say versions through 6.0.0.6 are affected. Patchstack, which is listed as the reference on each NVD record, names 6.0.0.7 as the patched release. That version is the current stable tag on WordPress.org, with a changelog dated November 17, 2026. If you still run 6.0.0.6 or earlier, update now.
The details below come from the four NVD records, the matching Patchstack advisories, and the official plugin changelog. This article does not reconstruct a proof of concept or describe how to trigger the flaws. None of those sources states that attacks have been observed in the wild, and this article does not add that claim.
What was published
All four CVE records were published on November 22, 2026, and describe issues in the plugin slug profilegrid-user-profiles-groups-and-communities. Each NVD entry uses a CVSS 3.1 score in the High range and says the product is affected “from n/a through 6.0.0.6.” The scores and privilege requirements below are the ones NVD published. The patched-version column is from the corresponding Patchstack advisory, which also recommends updating to 6.0.0.7 or later.
| CVE | Type (NVD) | CVSS 3.1 | Privileges / conditions (NVD) | Patched version (Patchstack) |
|---|---|---|---|---|
| CVE-2026-131705 | SQL Injection | 8.5 High | Network, low complexity, low privileges required, no user interaction, changed scope | 6.0.0.7 |
| CVE-2026-131706 | Blind SQL Injection | 7.5 High | Network, high complexity, no privileges required, no user interaction, changed scope. Patchstack lists this one as unauthenticated. | 6.0.0.7 |
| CVE-2026-131707 | PHP Object Injection (deserialization of untrusted data) | 8.8 High | Network, low complexity, low privileges required, no user interaction | 6.0.0.7 |
| CVE-2026-131708 | Reflected Cross-site Scripting | 7.1 High | Network, low complexity, no privileges required, user interaction required, changed scope | 6.0.0.7 |
NVD’s short descriptions stay at that level of detail: they name the weakness class and the affected version range, and they point to Patchstack. They do not publish exploit steps, and this article does not fill that gap. For CVE-2026-131707, an 8.8 score with high impact on confidentiality, integrity, and availability is a reason to treat object injection as urgent even when a site has no known gadget chain of its own — NVD does not say a chain is required, and this article does not speculate about one.
What the official 6.0.0.7 changelog says
WordPress.org lists ProfileGrid 6.0.0.7 as the stable tag. The plugin information API showed version 6.0.0.7, a last-updated timestamp of November 17, 2026, 11:02 a.m. GMT, and 5,000 active installations. The official changelog for 6.0.0.7, dated November 17, 2026, includes these security notes:
- Prevented group leaders from changing internal group options and blocked PHP object instantiation when stored group options are read, with thanks to Ananda Dhakal (Patchstack).
- Validated database update column identifiers and restricted editable group fields to prevent authenticated SQL injection, with thanks to Yuninha / Yannix-sec.
- Hardened authorization for user-data shortcodes and blocks, with thanks to wellknown.info.
- Hardened repayment authorization and payment-state protection, with thanks to Nguyen Hung Anh.
The same changelog entry also mentions a non-security fix for User Blogs Load More, which now refreshes expired security nonces and retries once if loading fails. That item is listed separately from the security bullets. The public changelog does not map each bullet to a CVE number, so this article does not invent those mappings. The first two bullets clearly address object-injection and authenticated SQL injection hardening. Patchstack still lists all four of the November 22 CVEs, including the unauthenticated blind SQL injection and the reflected XSS, as fixed in 6.0.0.7.
The mid-November patch date and the later CVE publication are a normal coordinated-disclosure pattern, not a sign that 6.0.0.7 is optional. If your dashboard still shows 6.0.0.6 or an older build, you do not have the fixes NVD is now cataloging.
How to update
In a standard WordPress site, open Dashboard → Updates or the Plugins screen and update ProfileGrid to 6.0.0.7 or later. Confirm that the installed version is at least 6.0.0.7 after the update finishes. You can also download the current release from the official WordPress.org plugin page. Do not install copies from unofficial mirrors.
If you cannot update immediately, Patchstack says it has issued a mitigation rule for these issues until a patched version is installed. That is a Patchstack-product statement, not a substitute for applying 6.0.0.7 on the site itself. This article does not recommend leaving a known-vulnerable plugin in place behind a virtual patch for longer than you have to.
Earlier ProfileGrid fixes are not a substitute
ProfileGrid already shipped other security work earlier this fall. The official changelog lists a PHP object-injection fix in 6.0.0.5 (October 21, 2026) and broader “security improvements” in 6.0.0.3 (September 30, 2026). Those releases do not take the place of 6.0.0.7. The November 22 CVE records explicitly include versions through 6.0.0.6.
This is a plugin update, not a WordPress core or PHP runtime patch. Recent coverage on this site has included the WordPress 7.1.5 security release, the Oxygen 6.2.2 SQL injection and XSS fixes, and the November 2026 PHP security updates. Those should stay on their own patch tracks. Sites that use ProfileGrid still need this plugin update even if core, PHP, or other plugins are already current.
Key facts
| Item | What official sources say |
|---|---|
| Plugin | ProfileGrid – User Profiles, Groups and Communities, by Metagauss, WordPress.org slug profilegrid-user-profiles-groups-and-communities. |
| CVE publication | November 22, 2026, in NVD, for CVE-2026-131705, CVE-2026-131706, CVE-2026-131707, and CVE-2026-131708. |
| Affected versions | NVD: through 6.0.0.6. Patchstack: update to 6.0.0.7 or later. |
| Highest listed score | CVE-2026-131707, CVSS 3.1 8.8 High (PHP object injection). |
| Vendor release | Official changelog for 6.0.0.7 dated November 17, 2026. WordPress.org stable tag 6.0.0.7; plugin API last updated November 17, 2026, 11:02 a.m. GMT. |
| Install base noted here | WordPress.org plugin API reported 5,000 active installations when checked for this article. |
| In-the-wild claims | The NVD records, Patchstack advisories, and official changelog reviewed for this article do not state that exploitation has been observed. This article does not add that claim. |
FAQ
What is ProfileGrid?
It is a free WordPress.org plugin from Metagauss for custom user profiles, groups, communities, memberships, directories, and related features. The official plugin page also describes WooCommerce and bbPress profile integrations. The WordPress.org plugin API reported 5,000 active installations when this article was prepared.
Which ProfileGrid versions are affected?
The four NVD records published on November 22, 2026, say the issues affect ProfileGrid through version 6.0.0.6. Patchstack lists 6.0.0.7 as the patched release for each of those CVEs. If you are still on 6.0.0.6 or earlier, you should update.
What is the most serious of the four CVEs?
On NVD’s CVSS 3.1 scores, CVE-2026-131707 is the highest at 8.8 High. NVD classifies it as PHP object injection from deserialization of untrusted data, with low privileges required and no user interaction. The other three records are also High: 8.5 and 7.5 for the SQL injection issues, and 7.1 for reflected XSS.
Are any of these issues unauthenticated?
Yes, according to NVD and Patchstack. CVE-2026-131706 is a blind SQL injection that NVD scores with no privileges required and high attack complexity; Patchstack labels it unauthenticated. CVE-2026-131708 is reflected XSS that NVD scores with no privileges required and user interaction required. CVE-2026-131705 and CVE-2026-131707 are scored with low privileges required.
When was the patch released?
The official changelog for ProfileGrid 6.0.0.7 is dated November 17, 2026, and WordPress.org lists that version as the current stable tag. The CVE records themselves were published on November 22, 2026. The later publication date does not mean you should wait; the fix is already in 6.0.0.7.
Does an earlier ProfileGrid update already cover this?
No. Earlier changelog entries describe other security work, including a PHP object-injection fix in 6.0.0.5, but the November 22 NVD records include versions through 6.0.0.6. Version 6.0.0.7 is the release Patchstack lists as the patch for these four CVEs.
Have these vulnerabilities been exploited in the wild?
The NVD records, Patchstack advisories, and official 6.0.0.7 changelog reviewed for this article do not state that attacks have been observed. This article does not add that claim. The practical step is still to update to 6.0.0.7 or later.
How do I update ProfileGrid?
Use the WordPress dashboard Updates or Plugins screen, or install the current package from the official WordPress.org plugin page, and confirm that the running version is 6.0.0.7 or later. Avoid unofficial download sites. Patchstack also describes a temporary mitigation rule in its product, but that is not a replacement for installing the patched plugin.

