RegistrationMagic <= 5.2.0.5 - Authenticated (Admin+) Insecure Direct Object Reference to Arbitrary User Password Change
Strategic Overview
- Status
- Patched in 5.2.1.0
- Affected Plugin
- RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
- Affected Version
<= 5.2.0.5- CVSS
- 6.6Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-2548
At a glance
CVE-2023-2548 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 5.2.0.5. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 5.2.1.0; sites on affected versions should update now. Disclosed May 2023, reported by István Márton.
Vulnerability Overview
The RegistrationMagic plugin for WordPress is vulnerable to Insecure Direct Object References in versions up to, and including, 5.2.0.5. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for authenticated attackers, with administrator-level permissions and above, to change user passwords and potentially take over super-administrator accounts in multisite setup.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in RegistrationMagic <= 5.2.0.5 takes an account at Admin level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For RegistrationMagic the fix is 5.2.1.0: builds <= 5.2.0.5 are affected, anything from 5.2.1.0 onward is not.
Remediation
Update to version 5.2.1.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: RegistrationMagic 5.2.1.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
- 9.9CVE-2020-9456: RegistrationMagic Privilege Escalation
CVE-2020-9456 - 9.9CVE-2020-9457: RegistrationMagic Settings Import
CVE-2020-9457 - 9.8CVE-2026-24373: RegistrationMagic Authentication Bypass
CVE-2026-24373 - 9.8CVE-2025-15403: RegistrationMagic <= 6.0.7.1 Privilege Escalation
CVE-2025-15403 - 9.8CVE-2024-10508: RegistrationMagic Privilege Escalation
CVE-2024-10508 - 9.8CVE-2023-2499: RegistrationMagic <= 5.2.1.0 Authentication Bypass
CVE-2023-2499 - 9.8CVE-2021-4073: RegistrationMagic <= 5.0.1.7 Authentication Bypass
CVE-2021-4073 - 9.8CVE-2017-20208: RegistrationMagic - Custom… PHP Object Injection
CVE-2017-20208
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C