CVE-2023-27459 is a deserialization flaw, PHP object injection, in the WPEverest User Registration plugin for WordPress. NVD scores it 7.4, High, and Patchstack says it needs a subscriber account. Versions up to 2.3.2.1 are affected and Patchstack lists 2.3.3 as the fixed release.
What's affected
- User Registration plugin 2.3.2.1 and earlier: affected, per the NVD record and Patchstack.
- User Registration 2.3.3: the fixed version listed by Patchstack.
Patchstack says the attacker needs an authenticated account at the Subscriber level. On a site where anyone can register, that is easy to obtain. No severity conflict: both NVD and Patchstack give 7.4.
How to check if you're exposed
If you have WP-CLI, run the following on the server.
wp plugin list --name=user-registration --fields=name,status,version,update
Otherwise open Plugins in the WordPress dashboard and read the version under User Registration. Anything at or below 2.3.2.1 needs the update. Also review whether public registration is switched on, because it decides who can obtain the account the attack needs.
What to do now
- Update the plugin to 2.3.3 or later from the dashboard, or with the command wp plugin update user-registration.
- If you cannot update at once, consider turning off open registration until you can.
- Review your user list for accounts you do not recognise, especially Subscriber accounts created in bulk.
- Take a backup before updating on a production site.
- Look at the Gold page for this CVE for later changes.
Why it matters
The record describes deserialization of untrusted data. The weakness class is CWE-502 (Deserialization of Untrusted Data). Deserialization turns stored data back into live objects. If an attacker controls the data, they can influence which objects are built and what code runs as a side effect when they are created or destroyed.
In PHP this is called object injection. The impact depends on which classes are available on the site, which is why the NVD vector rates confidentiality, integrity and availability all as high but sets attack complexity to high. The low-privilege entry point is what makes it worth a quick update.
Plugin flaws like this are usually found through code review and reported to the vendor first, which is why a patched version is available. The practical risk for site owners is the gap between the release and the update. Sites that run automatic plugin updates close that gap on their own. If yours do not, put a calendar reminder on a weekly plugin check.
A second habit helps more. Keep the list of installed plugins short. Every plugin adds code that runs with the site's own privileges, and deserialization bugs in particular tend to appear in features that store settings or form data as serialized values.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Why is a Subscriber account enough?
Because the vulnerable code path runs for logged-in users, and the lowest role is the only privilege Patchstack says is needed. Sites with open registration hand that out freely.
Sources
Last reviewed: 19 October 2026.