CVE-2022-0215

Login/Signup Popup <= 2.2 - Cross-Site Request Forgery to Arbitrary Options Update

2022-01-13 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 2.3
Affected Version
<= 2.2
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-0215
View all Login & Register Customizer – Forms, Popup, Profile & WooCommerce vulnerabilities

At a glance

CVE-2022-0215 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Login & Register Customizer WordPress plugin, affecting versions <= 2.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3; sites on affected versions should update now. Disclosed January 2022, reported by Chloe Chamberland.

Vulnerability Overview

The Login/Signup Popup, Waitlist Woocommerce ( Back in stock notifier ), and Side Cart Woocommerce (Ajax) WordPress plugins by XootiX are vulnerable to Cross-Site Request Forgery via the save_settings function found in the ~/includes/xoo-framework/admin/class-xoo-admin-settings.php file which makes it possible for attackers to update arbitrary options on a site that can be used to create an administrative user account and grant full privileged access to a compromised site. This affects versions <= 2.2 in Login/Signup Popup, versions <= 2.5.1 in Waitlist Woocommerce ( Back in stock notifier ), and versions <= 2.0 in Side Cart Woocommerce (Ajax).

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Login & Register Customizer <= 2.2 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 Login & Register Customizer the fix is 2.3: builds <= 2.2 are affected, anything from 2.3 onward is not.

Remediation

Update to version 2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Login & Register Customizer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Login & Register Customizer 2.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