CVE-2022-0420

RegistrationMagic <= 5.0.2.1 - SQL Injection

2022-02-07 00:00
qerogram

Strategic Overview

Status
Patched in 5.0.2.2
Affected Version
< 5.0.2.2
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2022-0420
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2022-0420 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the RegistrationMagic WordPress plugin, affecting versions < 5.0.2.2. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 5.0.2.2; sites on affected versions should update now. Disclosed February 2022, reported by qerogram.

Vulnerability Overview

The RegistrationMagic WordPress plugin before 5.0.2.2 does not sanitise and escape the rm_form_id parameter before using it in a SQL statement in the Automation admin dashboard, allowing high privilege users to perform SQL injection attacks

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-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in RegistrationMagic < 5.0.2.2 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For RegistrationMagic the fix is 5.0.2.2: builds < 5.0.2.2 are affected, anything from 5.0.2.2 onward is not.

Remediation

Update to version 5.0.2.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 5.0.2.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