RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login <= 6.0.9.7 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 6.0.9.8
- Affected Plugin
- RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
- Affected Version
<= 6.0.9.7- CVSS
- 8.1High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-73341
At a glance
CVE-2026-73341 is a high-severity Deserialization of Untrusted Data vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.9.7. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.0.9.8; sites on affected versions should update now. Disclosed August 2026, reported by dutafi.
Vulnerability Overview
The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.0.9.7. This is due to deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, 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-502: Deserialization of Untrusted Data
Reaching this weakness in RegistrationMagic <= 6.0.9.7 takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For RegistrationMagic the fix is 6.0.9.8: builds <= 6.0.9.7 are affected, anything from 6.0.9.8 onward is not.
Remediation
Update to version 6.0.9.8, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: RegistrationMagic 6.0.9.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
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 - 8.8CVE-2026-12158: RegistrationMagic CSRF to Privilege Escalation
CVE-2026-12158
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C