CVE-2026-12158

RegistrationMagic <= 6.0.9.1 - Cross-Site Request Forgery to Privilege Escalation via 'rmc_assign_user_role_action' Parameter

2026-06-30 19:50
Chloe Chamberland

Strategic Overview

Status
Patched in 6.0.9.2
Affected Version
<= 6.0.9.1
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-12158
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2026-12158 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.9.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 6.0.9.2; sites on affected versions should update now. Disclosed June 2026, reported by Chloe Chamberland.

Vulnerability Overview

The RegistrationMagic – User Registration Forms Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.0.9.1. This is due to missing or incorrect nonce validation on the process_request function. This makes it possible for unauthenticated attackers to escalate the privileges of an arbitrary form submitter to administrator by creating a malicious Chronos automation task that is executed via WordPress cron via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in RegistrationMagic <= 6.0.9.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For RegistrationMagic the fix is 6.0.9.2: builds <= 6.0.9.1 are affected, anything from 6.0.9.2 onward is not.

Remediation

Update to version 6.0.9.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to RegistrationMagic: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: RegistrationMagic 6.0.9.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C