ProfilegridWordPress extension · Metagauss
CVE-2022-36352
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 · uneditedMissing Authorization vulnerability in Profilegrid ProfileGrid – User Profiles, Memberships, Groups and Communities.This issue affects ProfileGrid – User Profiles, Memberships, Groups and Communities: from n/a through 5.0.3.
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 confidenceA missing authorization vulnerability in the ProfileGrid WordPress plugin versions through 5.0.3 allows unauthenticated or unauthorized users to access certain functionality that should be restricted, likely due to missing capability checks or nonce validation on sensitive admin or user actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ProfilegridWordPress extension
<= 5.0.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate ProfileGrid plugin installationAccess the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'ProfileGrid' or 'Metagauss Profilegrid' in the list of active and inactive plugins.Affected if ProfileGrid plugin is present in the WordPress installation regardless of activation status
-
Identify installed ProfileGrid versionIn the Plugins list, find the ProfileGrid entry and locate the version number displayed beneath the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/profilegrid-core/profilegrid.php and look for the 'Version' comment tag.Affected if The version listed is 5.0.3 or any version lower than 5.0.4
-
Check for unauthenticated access capabilityAttempt to access ProfileGrid user profile endpoints or admin actions without logging in or with a low-privilege user account. Common vulnerable endpoints include profile submission, group management, or user registration related to ProfileGrid.Affected if Sensitive user or admin actions complete successfully without proper authentication or without the user having required capabilities
-
Verify nonce validation on admin actionsInspect ProfileGrid source code in /wp-content/plugins/profilegrid-core/ for admin action handlers. Check if wp_nonce_field or check_admin_referer is present before processing privileged requests.Affected if Admin or user-facing actions process requests without validating nonces or checking user capabilities (like 'manage_options' or 'edit_users')
If ProfileGrid plugin version 5.0.3 or lower is installed and sensitive endpoints or admin actions can be accessed without authentication or proper capability checks, the environment is affected by CVE-2022-36352.
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 plugin to version 5.0.4 or later which contains the patched version addressing the authorization flaw.
Fix this in Profilegrid
Scoped from the published advisory
- 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-2022-36352 — 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-2022-36352 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