CVE-2024-23524

PilotPress <= 2.0.30 - Authenticated(Subscriber+) Missing Authorization via multiple AJAX functions

2024-01-31 00:00
Nguyen Xuan Chien

Strategic Overview

Status
Patched in 2.0.31
Affected Plugin
PilotPress
Affected Version
<= 2.0.30
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-23524
View all PilotPress vulnerabilities

At a glance

CVE-2024-23524 is a medium-severity Missing Authorization vulnerability in the PilotPress WordPress plugin, affecting versions <= 2.0.30. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.31; sites on affected versions should update now. Disclosed January 2024, reported by Nguyen Xuan Chien.

Vulnerability Overview

The PilotPress plugin for WordPress is vulnerable to unauthorized access to data and loss of data due to a missing capability check on multiple AJAX functions in all versions up to, and including, 2.0.30. This makes it possible for authenticated attackers, with subscriber access and above, to view reports and purge database transients.

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

Reaching this weakness in PilotPress <= 2.0.30 takes an account at Subscriber level or above. 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 PilotPress the fix is 2.0.31: builds <= 2.0.30 are affected, anything from 2.0.31 onward is not.

Remediation

Update to version 2.0.31, 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: PilotPress 2.0.31 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