CVE-2026-1054

RegistrationMagic <= 6.0.7.4 - Missing Authorization to Unauthenticated Arbitrary Settings Modification

2026-01-27 19:10
Md. Moniruzzaman Prodhan (NomanProdhan)

Strategic Overview

Status
Patched in 6.0.7.5
Affected Plugin
RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
Affected Version
<= 6.0.7.4
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1054
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2026-1054 is a medium-severity Missing Authorization vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 6.0.7.4. 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.5; sites on affected versions should update now. Disclosed January 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

The RegistrationMagic plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 6.0.7.4. This is due to missing nonce verification and capability checks on the rm_set_otp AJAX action handler. This makes it possible for unauthenticated attackers to modify arbitrary plugin settings, including reCAPTCHA keys, security settings, and frontend menu titles.

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-862: Missing Authorization

Reaching this weakness in RegistrationMagic <= 6.0.7.4 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For RegistrationMagic the fix is 6.0.7.5: builds <= 6.0.7.4 are affected, anything from 6.0.7.5 onward is not.

Remediation

Update to version 6.0.7.5, 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.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1054https://www.wordfence.com/threat-intel/vulnerabilities/id/daf4d246-85f3-48b3-985f-982fea4772f1https://nvd.nist.gov/vuln/detail/CVE-2026-1054

Related records

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