RegistrationMagic accepts Facebook tokens issued to other applications
RegistrationMagic 5.0.1.8 through 6.0.9.8 does not verify that a Facebook access token was issued for the site's configured application. An unauthenticated attacker with a token for an existing user can log in as that user, or create and enter a new account even when WordPress registration is disabled.
- Component
- RegistrationMagic
- Plugin slug
registrationmagic- Affected
- 5.0.1.8 to < 6.0.9.9
- Safe version
6.0.9.9- Published
- Sep 05, 2026
This CVE was published Sep 05, 2026 and is one of 18 known issues for this plugin.
Update, patch or deactivate.
Update to RegistrationMagic 6.0.9.9 or later, rotate relevant social-login credentials, and audit accounts and sessions created through Facebook authentication.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The RegistrationMagic WordPress plugin before 6.0.9.9 does not verify which application a Facebook access token was issued to before accepting it as proof of identity, allowing 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H