CVE-2023-25991

RegistrationMagic <= 5.1.9.2 - Cross-Site Request Forgery leading to Form Metadata Deletion

2023-02-17 00:00
Rafshanzani Suhada

Strategic Overview

Status
Patched in 5.1.9.3
Affected Version
<= 5.1.9.2
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-25991
View all RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login vulnerabilities

At a glance

CVE-2023-25991 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the RegistrationMagic WordPress plugin, affecting versions <= 5.1.9.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.1.9.3; sites on affected versions should update now. Disclosed February 2023, reported by Rafshanzani Suhada.

Vulnerability Overview

The RegistrationMagic plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.1.9.2. This is due to missing or incorrect nonce validation on the 'remove' function inside the 'class_rm_form_controller.php' file. This makes it possible for unauthenticated attackers to remove certain form metadata 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 privileges on the target site.

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

RegistrationMagic <= 5.1.9.2 carries this weakness at remove, and reaching it 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 5.1.9.3: builds <= 5.1.9.2 are affected, anything from 5.1.9.3 onward is not.

Remediation

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