CVE-2024-54336

Projectopia <= 5.1.7 - Missing Authorization to Privilege Escalation via pto_reset_password()

2024-12-11 00:00
stealthcopter

Strategic Overview

Status
Patched in 5.1.8
Affected Version
<= 5.1.7
CVSS
9.8Critical
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-54336
View all Projectopia – Project Management Tool vulnerabilities

At a glance

CVE-2024-54336 is a critical-severity Missing Authorization vulnerability in the Projectopia WordPress plugin, affecting versions <= 5.1.7. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 5.1.8; sites on affected versions should update now. Disclosed December 2024, reported by stealthcopter.

Vulnerability Overview

The Projectopia – WordPress Project Management plugin for WordPress is vulnerable to privilege escalation via account takeover via the pto_reset_password function in all versions up to, and including, 5.1.7. This makes it possible for unauthenticated attackers to elevate their privilege level and gain access to administrator accounts.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in Projectopia <= 5.1.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 Projectopia the fix is 5.1.8: builds <= 5.1.7 are affected, anything from 5.1.8 onward is not.

Remediation

Update to version 5.1.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: Projectopia 5.1.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