CVE-2020-9457

RegistrationMagic – Custom Registration Forms and User Login <= 4.6.0.3 - Authenticated Settings Import to Privilege Escalation

2020-03-05 00:00
Ram

Strategic Overview

Status
Patched in 4.6.0.4
Affected Plugin
RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login
Affected Version
<= 4.6.0.3
CVSS
9.9Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2020-9457
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2020-9457 is a critical-severity Missing Authorization vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 4.6.0.3. It carries a CVSS score of 9.9 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.6.0.4; sites on affected versions should update now. Disclosed March 2020, reported by Ram.

Vulnerability Overview

The RegistrationMagic plugin through 4.6.0.3 for WordPress allows remote authenticated users (with minimal privileges) to import custom vulnerable forms and change form settings via class_rm_form_settings_controller.php, resulting in privilege escalation.

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

Reaching this weakness in RegistrationMagic <= 4.6.0.3 takes any authenticated account. 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 4.6.0.4: builds <= 4.6.0.3 are affected, anything from 4.6.0.4 onward is not.

Remediation

Update to version 4.6.0.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: RegistrationMagic 4.6.0.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2020-9457https://www.wordfence.com/threat-intel/vulnerabilities/id/e7939401-822c-4d27-9d8c-c5680165e6a7https://nvd.nist.gov/vuln/detail/CVE-2020-9457

Related records

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