CVE-2022-45083 is a medium severity (CVSS 6.6) deserialization of untrusted data flaw in the ProfilePress membership plugin for WordPress, versions up to and including 4.3.2. It needs an administrator account to trigger. Update to ProfilePress 4.4.0 or later. Check your installed version and apply the update through your normal change process.
What's affected
The record lists ProfilePress from ProfilePress Membership Team, from the first release through 4.3.2. Patchstack gives the patched version as 4.4.0. Patchstack gives the required privilege as Administrator.
The record scores it 6.6 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L. Patchstack labels its own priority Low. The weakness class is CWE-502 (Deserialization of Untrusted Data).
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 wp-user-avatar. 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 4.3.2 or lower is affected. Version 4.4.0 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 ProfilePress to 4.4.0 or a newer release.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the plugin so the next fix lands without a ticket.
Why it matters
Deserialization turns stored text back into live objects. If the text comes from someone untrusted, they may be able to choose which objects are built, and PHP classes that run code when created or destroyed can then be misused. The class is called PHP object injection, and the record files it as deserialization of untrusted data.
Here the vector needs high privileges, which is why the score stays at medium, and Patchstack agrees by listing Administrator as the required role and rating its own priority Low. The scope is marked changed, which hints at reach beyond the plugin if a usable chain exists on the site.
Whether a usable chain exists depends on the other code installed, which is why the advisory language stays general. An administrator account is a high bar, but compromised admin credentials are common, and this is a case where one weakness can make another worse. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need to worry if only trusted people are administrators?
The immediate risk is lower, but admin accounts get phished and reused. Patch anyway, and keep the administrator list short.
Which version fixes it?
Patchstack lists 4.4.0.
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.