CVE-2025-13610

An unauthenticated attacker can perform PHP Object Injection in RegistrationMagic versions up to 6.0.9.7.

Versions of RegistrationMagic up to 6.0.8.6 have a vulnerability in unauthenticated authentication, which may allow attackers to take over user accounts.

The RegistrationMagic WordPress plugin before version 6.0.9.9 does not verify which application a Facebook access token was issued to before accepting it as proof of identity. This allows unauthenticated attackers to log in as an existing user whose token they can obtain, or to create and log into a new account even when user registration is disabled.

The RegistrationMagic WordPress plugin before version 6.0.9.9 does not validate a client-supplied quantity multiplier when calculating the total price of a paid registration, allowing unauthenticated users to register without paying and obtain an activated account holding the role the form grants.

The RegistrationMagic WordPress plugin before version 6.0.9.9 does not validate the total price of a paid registration server-side, allowing unauthenticated users to complete a paid registration without paying and obtain an activated account.

The RegistrationMagic WordPress plugin before 6.0.9.9 does not escape a registration form field value before outputting it in an HTML attribute on an administrative page. This allows unauthenticated users to perform Stored Cross-Site Scripting attacks against high privilege users such as admin.

An unauthenticated broken authentication vulnerability in RegistrationMagic versions up to and including 6.0.9.8.

An unauthenticated Cross Site Scripting (XSS) vulnerability in RegistrationMagic versions up to and including 6.0.9.8.

The RegistrationMagic WordPress plugin before version 6.0.9.4 does not sanitize and escape a parameter before using it in a SQL statement, which could allow high privilege users such as admin to perform SQL injection attacks.

The RegistrationMagic WordPress plugin before 6.0.9.5 does not compare the verified PayPal capture's amount, currency, payee, or prior use against the registration it is finalising: its server-side check only confirms the capture status is COMPLETED. An unauthenticated attacker can therefore finalise an expensive paid registration with any genuinely-completed low-value capture, and replay a single capture across unlimited registrations because captures are not de-duplicated.