CVE-2024-22151

Import and export users and customers <= 1.24.6 - Missing Authorization via fire_cron REST endpoint

2024-01-16 00:00
emad

Strategic Overview

Status
Patched in 1.24.7
Affected Version
<= 1.24.6
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-22151
View all Import and export users and customers vulnerabilities

At a glance

CVE-2024-22151 is a medium-severity Missing Authorization vulnerability in the Import and export users and customers WordPress plugin, affecting versions <= 1.24.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.24.7; sites on affected versions should update now. Disclosed January 2024, reported by emad.

Vulnerability Overview

The Import and export users and customers plugin for WordPress is vulnerable to unauthorized modification of data due to an improper capability check on the fire_cron function in versions up to, and including, 1.24.6. This makes it possible for unauthenticated attackers to trigger the plugin's cron job.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Import and export users and customers <= 1.24.6 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 Import and export users and customers the fix is 1.24.7: builds <= 1.24.6 are affected, anything from 1.24.7 onward is not.

Remediation

Update to version 1.24.7, 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: Import and export users and customers 1.24.7 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