Login/Signup Popup <= 2.3 - Cross-Site Request Forgery to Settings Reset

2023-06-26 00:00
Anonymous

Strategic Overview

Status
Patched in 2.4
Affected Plugin
Login & Register Customizer – Forms, Popup, Profile & WooCommerce
Affected Version
< 2.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Login & Register Customizer – Forms, Popup, Profile & WooCommerce vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Login & Register Customizer WordPress plugin, affecting versions < 2.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4; sites on affected versions should update now. Disclosed June 2023.

Vulnerability Overview

The Login/Signup Popup plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3. This is due to missing nonce validation on the reset_settings() function. This makes it possible for unauthenticated attackers to reset the plugin's settings 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)

Login & Register Customizer < 2.4 carries this weakness at reset_settings(), 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 Login & Register Customizer the fix is 2.4: builds < 2.4 are affected, anything from 2.4 onward is not.

Remediation

Update to version 2.4, 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.4 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/3fa62b8f-1c2f-4bc9-9f2a-8b9765c2d30d

Related records

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