WordPress security changelog
MEDIUM CVE-2026-9242 Deferred

RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login: Privilege escalation or authentication bypass

RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess. The published affected range is <= 6.0.8.6.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
Plugin slug
custom-registration-form-builder-with-submission-manager
Affected
<= 6.0.8.6
Safe version
> 6.0.8.6
Published
Jun 27, 2026
Weakness
CWE-345 — Insufficient Verification of Data Authenticity

This CVE was published Jun 27, 2026 and is one of 37 known issues for this plugin.

What to do

Update, patch or deactivate.

Update RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login to a release after 6.0.8.6, or disable and remove it until a fixed version is available.

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.

Source record

Technical description

The RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Verification of Data Authenticity in all versions up to and including 6.0.8.6. This is due to the PayPal IPN `callback` handler being registered as a nopriv AJAX action with no authentication or nonce requirement, and critically because the handler updates the payment log database row with attacker-controlled POST data — including `payment_status` and the `custom` field encoding the target `user_id` — before PayPal IPN validation is performed, meaning the database remains poisoned even when validation subsequently fails. This makes it possible for unauthenticated attackers to authenticate as any WordPress user, including administrators, by submitting a forged IPN request that overwrites a payment log entry's `user_id` with that of a target account, then visiting the success return URL with a legitimately obtained security hash to cause the plugin to issue real WordPress authentication cookies for the targeted account.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources