CVE-2023-4916

Login with phone number <= 1.5.6 - Cross-Site Request Forgery to User Password Change

2023-09-12 00:00
István Márton

Strategic Overview

Status
Patched in 1.5.7
Affected Plugin
OTP Login With Phone Number, OTP Verification
Affected Version
<= 1.5.6
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-4916
View all OTP Login With Phone Number, OTP Verification vulnerabilities

At a glance

CVE-2023-4916 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the OTP Login With Phone Number, OTP Verification WordPress plugin, affecting versions <= 1.5.6. 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 1.5.7; sites on affected versions should update now. Disclosed September 2023, reported by István Márton.

Vulnerability Overview

The Login with phone number plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.6. This is due to missing nonce validation on the 'lwp_update_password_action' function. This makes it possible for unauthenticated attackers to change user password 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

OTP Login With Phone Number, OTP Verification <= 1.5.6 carries this weakness at lwp_update_password_action, 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 OTP Login With Phone Number, OTP Verification the fix is 1.5.7: builds <= 1.5.6 are affected, anything from 1.5.7 onward is not.

Remediation

Update to version 1.5.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to OTP Login With Phone Number, OTP Verification: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OTP Login With Phone Number, OTP Verification 1.5.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4916https://www.wordfence.com/threat-intel/vulnerabilities/id/71083db7-377b-47a1-ac8b-83d8974a2654https://nvd.nist.gov/vuln/detail/CVE-2023-4916

Related records

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