CVE-2022-42884

WIP Custom Login <= 1.2.7 - Missing Authorization

2022-10-24 00:00
István Márton

Strategic Overview

Status
Patched in 1.2.8
Affected Plugin
WIP Custom Login
Affected Version
<= 1.2.7
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-42884
View all WIP Custom Login vulnerabilities

At a glance

CVE-2022-42884 is a medium-severity Missing Authorization vulnerability in the WIP Custom Login WordPress plugin, affecting versions <= 1.2.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.2.8; sites on affected versions should update now. Disclosed October 2022, reported by István Márton.

Vulnerability Overview

The WIP Custom Login plugin for WordPress is vulnerable to authorization bypass due to a missing capability and nonce check on several the wip_custom_login_backup_reset action in versions up to, and including, 1.2.7. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke the function to reset the plugin's back-up.

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Reaching this weakness in WIP Custom Login <= 1.2.7 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 WIP Custom Login the fix is 1.2.8: builds <= 1.2.7 are affected, anything from 1.2.8 onward is not.

Remediation

Update to version 1.2.8, 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: WIP Custom Login 1.2.8 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