CVE-2024-5665

Login/Signup Popup ( Inline Form + Woocommerce ) 2.7.1 - 2.7.2 - Missing Authorization to Arbitrary Options Exposure

2024-06-05 19:24
1337_Wannabe

Strategic Overview

Status
Patched in 2.7.3
Affected Version
2.7.1 – 2.7.2
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-5665
View all Login & Register Customizer – Forms, Popup, Profile & WooCommerce vulnerabilities

At a glance

CVE-2024-5665 is a medium-severity Missing Authorization vulnerability in the Login & Register Customizer WordPress plugin, affecting versions 2.7.1 – 2.7.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.7.3; sites on affected versions should update now. Disclosed June 2024, reported by 1337_Wannabe.

Vulnerability Overview

The Login/Signup Popup ( Inline Form + Woocommerce ) plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ‘export_settings’ function in versions 2.7.1 to 2.7.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read arbitrary options on affected sites.

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.

CWE-862: Missing Authorization

Login & Register Customizer 2.7.1 – 2.7.2 carries this weakness at export_settings, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Login & Register Customizer the fix is 2.7.3: builds 2.7.1 – 2.7.2 are affected, anything from 2.7.3 onward is not.

Remediation

Update to version 2.7.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Login & Register Customizer 2.7.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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