Tag: security update

  • ProfileGrid 6.0.0.7 Patches High-Severity SQL Injection and Object Injection (2026)

    ProfileGrid 6.0.0.7 Patches High-Severity SQL Injection and Object Injection (2026)

    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.

    CVEType (NVD)CVSS 3.1Privileges / conditions (NVD)Patched version (Patchstack)
    CVE-2026-131705SQL Injection8.5 HighNetwork, low complexity, low privileges required, no user interaction, changed scope6.0.0.7
    CVE-2026-131706Blind SQL Injection7.5 HighNetwork, high complexity, no privileges required, no user interaction, changed scope. Patchstack lists this one as unauthenticated.6.0.0.7
    CVE-2026-131707PHP Object Injection (deserialization of untrusted data)8.8 HighNetwork, low complexity, low privileges required, no user interaction6.0.0.7
    CVE-2026-131708Reflected Cross-site Scripting7.1 HighNetwork, low complexity, no privileges required, user interaction required, changed scope6.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

    ItemWhat official sources say
    PluginProfileGrid – User Profiles, Groups and Communities, by Metagauss, WordPress.org slug profilegrid-user-profiles-groups-and-communities.
    CVE publicationNovember 22, 2026, in NVD, for CVE-2026-131705, CVE-2026-131706, CVE-2026-131707, and CVE-2026-131708.
    Affected versionsNVD: through 6.0.0.6. Patchstack: update to 6.0.0.7 or later.
    Highest listed scoreCVE-2026-131707, CVSS 3.1 8.8 High (PHP object injection).
    Vendor releaseOfficial 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 hereWordPress.org plugin API reported 5,000 active installations when checked for this article.
    In-the-wild claimsThe 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.

  • GPGME 2.3.1 Fixes a Critical Double-Free (CVE-2026-129975)

    GPGME 2.3.1 Fixes a Critical Double-Free (CVE-2026-129975)

    Takeaway: On November 20, 2026, the GnuPG project issued a security advisory for GPGME, the library many programs use to talk to GnuPG. Werner Koch announced GPGME 2.3.1, which fixes CVE-2026-129975, a critical double-free in all prior public versions. The project says a crafted OpenPGP key with a very long user ID can trigger the bug, that the flaw can be used to exfiltrate data from affected applications — for example by sending signed data — and that a remote code execution attack cannot be ruled out. It strongly suggests an immediate update.

    The details below come from that official gnupg-announce message. This article does not reconstruct a proof of concept or describe how to craft such a key. GPGME 2.3.1 is the fixed public release; the advisory notes that version 2.3.0 was never publicly available.

    What the advisory describes

    GPGME is the standard library applications use to work with GnuPG, whether it is loaded as a shared library, a Windows DLL, or statically linked into a program. The bug, tracked internally as T8557 and publicly as CVE-2026-129975, sits in two internal functions that read status lines and key listings coming back from gpg.

    According to the advisory, those functions start with a 1,024-byte buffer and reallocate it when more space is required. The new buffer pointer is used inside the function, but it is assigned back to the context object only at the end. If the function returns early — for example because of a read error — the context can keep a stale pointer to memory that was already freed. When the context is later released, that memory can be freed a second time. The project notes that other allocations in between may mean common double-free checks in memory allocators are not triggered.

    The trigger described in the announcement is an OpenPGP key that contains a crafted, very long user ID. The project says this double-free can be used to exfiltrate data from applications, and that exploiting it for remote code execution cannot be ruled out. It does not report whether attacks have been observed, and this article does not add that claim.

    Who is affected

    The advisory says all software using a GPGME version prior to 2.3.0 — as a shared library, DLL, or statically linked binary — is affected. Examples it gives include:

    • Gpg4win
    • GnuPG Desktop
    • GnuPG VS-Desktop
    • Most mail clients
    • Many XMPP clients
    • Samba
    • Flatpack, which is the spelling used in the announcement

    The list is illustrative, not exhaustive. Any other program that links GPGME on the same terms is in the same class. The announcement also says there is no need to update GPGMEPP or GPGMEQT for this fix.

    How to update

    The project’s recommended fix is to update the GPGME shared library to version 2.3.1. Windows users who need a DLL can take it from the updated Gpg4win package; the announcement says Gpg4win 5.1.2, which includes the fixed library, the Kleopatra GUI, and a PDF reader, has been released at gpg4win.org. New GnuPG Desktop and GnuPG VS-Desktop versions that use the fixed library were also released.

    If a program statically links GPGME, the advisory says it must be rebuilt against GPGME 2.3.1. If the library cannot be updated for some reason, the announcement includes a patch that the project says likely applies cleanly even to very old versions. Source and a signature are published at the project’s usual download locations, including gpgme-2.3.1.tar.bz2. The announcement also points to Debian-style packages at repos.gnupg.org and to the project’s integrity-check instructions. Verify downloads against those official instructions rather than a checksum copied from a third-party article.

    Compared with GPGME 2.2.0, version 2.3.1 also adds algorithm-mapping constants — GPGME_PK_MLKEM, GPGME_PK_MLDSA, and GPGME_PK_DLTHM — alongside the security fix. Those additions are listed in the announcement’s noteworthy-changes section; they are not a substitute for installing the double-free patch.

    Disclosure timeline

    The vulnerability was discovered by Johan Carlsson. The project says GitLab informed it on November 12, 2026, and that a coordinated disclosure had been set for November 25. Because of what the announcement calls the new Ruby2Shell bug, GitLab had to update earlier, and GnuPG also disclosed the GPGME bug on November 20, 2026. The noteworthy-changes block dates the 2.3.1 release to November 19, 2026. This article does not expand the Ruby2Shell reference beyond that official explanation for the earlier date.

    How this differs from other recent security updates

    This is a library update in the GnuPG stack, not a web-server, hypervisor, or language-runtime patch. Recent coverage on this site has included the November 2026 PHP security releases, F5’s out-of-band BIG-IP notification, and VMware VMSA-2026-0009. Those advisories cover different products and should be handled on their own patch tracks. GPGME 2.3.1 is specifically for applications and installers that bundle or link this library.

    Key facts

    ItemWhat official sources say
    AdvisoryGnuPG security advisory for GPGME, posted to gnupg-announce on November 20, 2026, by Werner Koch.
    IdentifierCVE-2026-129975; project tracker T8557.
    FlawA double-free in functions that read GnuPG status lines and key listings, triggerable by an OpenPGP key with a crafted, very long user ID.
    Impact statedData exfiltration from affected applications is possible, for example via signed data. Remote code execution cannot be ruled out. Immediate update is strongly suggested.
    Affected versionsAll software using GPGME prior to 2.3.0, including shared libraries, DLLs, and statically linked binaries. Version 2.3.0 was never publicly available. The fixed public release is 2.3.1 (November 19, 2026).
    Examples namedGpg4win, GnuPG Desktop, GnuPG VS-Desktop, most mail clients, many XMPP clients, Samba, and Flatpack, as spelled in the advisory.
    FixesUpdate the shared library to 2.3.1; rebuild statically linked programs against 2.3.1; or apply the project’s attached patch. Gpg4win 5.1.2 includes the fixed library. GPGMEPP and GPGMEQT do not need an update for this bug.
    Credit and timingDiscovered by Johan Carlsson; reported via GitLab on November 12, 2026; disclosed November 20 after a planned November 25 date was moved up.

    FAQ

    What is CVE-2026-129975?

    It is a critical double-free in GPGME, the library programs use to work with GnuPG. The official advisory says an OpenPGP key with a crafted, very long user ID can trigger it in the code that reads status lines and key listings from GnuPG.

    Which GPGME version fixes the bug?

    GPGME 2.3.1, dated November 19, 2026, in the announcement’s noteworthy-changes list. The advisory says version 2.3.0 was never publicly available, so 2.3.1 is the fixed public release.

    Does this affect only GnuPG’s own apps?

    No. The advisory says all software using a GPGME version prior to 2.3.0 is affected, whether the library is shared, a Windows DLL, or statically linked. Besides Gpg4win and the GnuPG desktop packages, it names most mail clients, many XMPP clients, Samba, and Flatpack as examples.

    Can this bug be used for remote code execution?

    The project says a remote code execution attack cannot be ruled out. It also says the double-free can be used to exfiltrate data from applications, for example by sending signed data. It strongly suggests updating immediately. This article does not add exploit details.

    What should Windows users install?

    The announcement points Windows users who need a DLL to the updated Gpg4win package and says Gpg4win 5.1.2 includes the fixed GPGME library, Kleopatra, and a PDF reader. Download it from the official Gpg4win site and follow GnuPG’s integrity-check guidance.

    What if our software statically links GPGME?

    The advisory says statically linked binaries need to be rebuilt against GPGME 2.3.1. If the library cannot be updated, the announcement includes a patch that the project says likely applies even to very old versions.

    Do GPGMEPP or GPGMEQT need a separate update?

    The announcement says there is no need to update GPGMEPP or GPGMEQT for this fix. The required change is in GPGME itself.

    Why was the bug disclosed before November 25?

    GnuPG says GitLab informed it on November 12 and that coordinated disclosure had been set for November 25. Because of a new Ruby2Shell bug, GitLab had to update earlier, and GnuPG disclosed the GPGME issue on November 20, 2026.