CVE-2022-36352 is a medium severity (CVSS 6.3) missing authorization flaw in the ProfileGrid WordPress plugin for user profiles, memberships and groups, versions up to and including 5.0.3. A Subscriber level account is enough. Update to 5.0.4 or later. Check your installed version and apply the update through your normal change process.
What's affected
The record lists ProfileGrid from the first release through 5.0.3. Patchstack gives the patched version as 5.0.4 and the required privilege as Subscriber.
The record scores the issue 6.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. Patchstack labels its own priority as High. Both statements can be true: the CVSS number is middling, but ProfileGrid exists to let visitors register and join groups, so the Subscriber requirement is easy to meet on a typical site. The class is CWE-862 (Missing Authorization).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder profilegrid-user-profiles-groups-and-communities. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 5.0.3 or lower is affected, and 5.0.4 or later is patched.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.
What to do now
- Update ProfileGrid to 5.0.4 or later.
- If registration is open, check the user list for accounts you do not recognise and remove them.
- Review group, membership and profile settings for unexpected changes.
- Enable auto updates for the plugin.
Why it matters
A missing authorization check is one of the most common WordPress plugin bugs. The plugin exposes an action to logged in users and trusts that the caller is permitted, without testing the caller's capability. Any account, including a freshly registered Subscriber, can then reach functionality meant for administrators or group owners.
The exact action is not described in the record, and the Patchstack summary stays at the class level, so I will not guess at it. What you can rely on is the scoring: low confidentiality, integrity and availability impact each, reachable over the network with low privileges. The record's KEV flag is false and no exploitation is reported in what I read.
Quick check
Why does Patchstack say High priority when the score is 6.3?
Patchstack ranks practical risk for WordPress sites, where open registration lowers the bar. The NVD style score only measures the technical severity. Treat the plugin update as a priority.
Do I need to patch if registration is closed?
The exposure shrinks, but any existing low privilege account can still use the flaw, so patch anyway.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.