CVE-2023-23976 is a high severity incorrect default permissions flaw (CVSS 7.5) in the RegistrationMagic WordPress plugin, affecting every version through 5.1.9.2. Update to 5.1.9.3 or later. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.
What's affected
- RegistrationMagic plugin, all versions up to and including 5.1.9.2, per the record and the Patchstack listing.
- Fixed version: 5.1.9.3, per Patchstack.
- Patchstack files this under OWASP Top 10 security misconfiguration.
- Severity: CVSS 3.1 score 7.5 High, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
How to check if you're exposed
If you manage the site with WP-CLI, list the plugin and its version:
wp plugin list --fields=name,version,status | grep -i custom-registration-form-builder-with-submission-manager
The plugin directory slug is custom-registration-form-builder-with-submission-manager. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the RegistrationMagic entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.
What to do now
- Find every WordPress site that has RegistrationMagic installed, including staging copies, and read the version.
- Update the plugin to 5.1.9.3 or later and confirm the version in the plugin list.
- If the plugin handles payments, review recent orders and compare amounts with your payment provider.
- If you cannot update right away, deactivate the plugin until you can.
- Review web server logs for unexpected requests to the plugin around the time you learned of the issue.
Why it matters
The weakness is incorrect default permissions (CWE-276 (Incorrect Default Permissions)). Functionality that should be limited to administrators is reachable by people who should not have it, because the default access rules are too loose. The record describes it as accessing functionality not properly constrained by ACLs.
The vector shows network access, no privileges, no user interaction and a high integrity impact. The Patchstack title mentions an arbitrary price change, which suggests orders or paid registrations could be altered by an anonymous visitor. If your site takes payments through the plugin, review recent orders for prices that look wrong. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
Roles matter here. Review which accounts exist on your site, remove the ones nobody uses, and give the remaining people only the role they need. Fewer low privilege accounts means fewer ways to turn a plugin flaw into a problem.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
What is the main risk?
Per the Patchstack title, changing prices. The vector shows high integrity impact and no confidentiality or availability impact.
How do I check recent orders?
Compare payment records in your payment provider with the orders the plugin shows, looking for amounts that do not match your price list.
Sources
Last reviewed: 19 October 2026.