CVE-2024-10097

Loginizer Security and Loginizer <= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider

2024-11-04 00:00
wesley (wcraft)

Strategic Overview

Status
Patched in 1.9.3
Affected Plugin
Loginizer
Affected Version
<= 1.9.2
CVSS
8.1High
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2024-10097
View all Loginizer vulnerabilities

At a glance

CVE-2024-10097 is a high-severity Improper Authentication vulnerability in the Loginizer WordPress plugin, affecting versions <= 1.9.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.9.3; sites on affected versions should update now. Disclosed November 2024, reported by wesley (wcraft).

Vulnerability Overview

The Loginizer Security and Loginizer plugins for WordPress are vulnerable to authentication bypass in all versions up to, and including, 1.9.2. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-287: Improper Authentication

Reaching this weakness in Loginizer <= 1.9.2 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Loginizer the fix is 1.9.3: builds <= 1.9.2 are affected, anything from 1.9.3 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-10097https://www.wordfence.com/threat-intel/vulnerabilities/id/5db00b22-d766-4fde-86fe-98d90936028chttps://nvd.nist.gov/vuln/detail/CVE-2024-10097

Related records

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