CVE-2020-8435

RegistrationMagic - Custom Registration Forms, User Registration and User Login Plugin <= 4.6.0.2 - SQL Injection

2020-02-13 00:00
Anonymous

Strategic Overview

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

At a glance

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

Vulnerability Overview

An issue was discovered in the RegistrationMagic plugin 4.6.0.2 for WordPress. There is SQL injection via the rm_analytics_show_form rm_form_id parameter.

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, availability.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

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

Remediation

Update to version 4.6.0.3, 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 4.6.0.3 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