RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login <= 6.0.6.9 - Unauthenticated Payment Bypass via rm_process_paypal_sdk_payment
Strategic Overview
- Status
- Patched in 6.0.7.0
- Affected Plugin
- RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
- Affected Version
<= 6.0.6.9- CVSS
- 5.3Medium
- Weakness type
- CWE-345 · Insufficient Verification of Data Authenticity
- CVE
CVE-2025-14444
At a glance
CVE-2025-14444 is a medium-severity Insufficient Verification of Data Authenticity vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.6.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.7.0; sites on affected versions should update now. Disclosed February 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to payment bypass due to insufficient verification of data authenticity on the 'process_paypal_sdk_payment' function in all versions up to, and including, 6.0.6.9. This is due to the plugin trusting client-supplied values for payment verification without validating that the payment actually went through PayPal. This makes it possible for unauthenticated attackers to bypass paid registration by manipulating payment status and activating their account without completing a real PayPal payment.
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.
CWE-345: Insufficient Verification of Data Authenticity
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Remediation
Update to version 6.0.7.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: RegistrationMagic 6.0.7.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