CVE-2024-43916

Zephyr Project Manager <= 3.3.102 - Missing Authorization to Authenticated (Subscriber+) Status Updates

2024-08-20 00:00
Trương Hữu Phúc (truonghuuphuc)

Strategic Overview

Status
Patched in 3.3.103
Affected Plugin
Zephyr Project Manager
Affected Version
<= 3.3.102
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-43916
View all Zephyr Project Manager vulnerabilities

At a glance

CVE-2024-43916 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Zephyr Project Manager WordPress plugin, affecting versions <= 3.3.102. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.103; sites on affected versions should update now. Disclosed August 2024, reported by Trương Hữu Phúc (truonghuuphuc).

Vulnerability Overview

The Zephyr Project Manager plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the via the 'create_status‘, ‘update_status‘, and ‘delete_status‘ functions in all versions up to, and including, 3.3.102. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update statuses.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Zephyr Project Manager <= 3.3.102 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Zephyr Project Manager the fix is 3.3.103: builds <= 3.3.102 are affected, anything from 3.3.103 onward is not.

Remediation

Update to version 3.3.103, 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: Zephyr Project Manager 3.3.103 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-43916https://www.wordfence.com/threat-intel/vulnerabilities/id/6746d20c-d528-4c69-95e4-9f22d6460463https://nvd.nist.gov/vuln/detail/CVE-2024-43916

Related records

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