RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login <= 6.0.7.1 - Authentication Bypass
Strategic Overview
- Status
- Patched in 6.0.7.2
- Affected Plugin
- RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
- Affected Version
<= 6.0.7.1- CVSS
- 9.8Critical
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-24373
At a glance
CVE-2026-24373 is a critical-severity Improper Authentication vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.7.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.0.7.2; sites on affected versions should update now. Disclosed March 2026, reported by 0xd4rk5id3.
Vulnerability Overview
The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 6.0.7.1. This makes it possible for unauthenticated attackers to bypass authentication.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Reaching this weakness in RegistrationMagic <= 6.0.7.1 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For RegistrationMagic the fix is 6.0.7.2: builds <= 6.0.7.1 are affected, anything from 6.0.7.2 onward is not.
Remediation
Update to version 6.0.7.2, 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 6.0.7.2 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-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-2017-20208: RegistrationMagic - Custom… PHP Object Injection
CVE-2017-20208 - 8.8CVE-2026-12158: RegistrationMagic CSRF to Privilege Escalation
CVE-2026-12158 - 8.8CVE-2024-1990: RegistrationMagic SQL Injection
CVE-2024-1990
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C