CVE-2024-6698

FundEngine – Donation and Crowdfunding Platform <= 1.7.0 - Authenticated (Subscriber+) Privilege Escalation

2024-07-31 15:16
Thanh Nam Tran

Strategic Overview

Status
Patched in 1.7.1
Affected Version
<= 1.7.0
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-6698
View all FundEngine – Donation and Crowdfunding Platform vulnerabilities

At a glance

CVE-2024-6698 is a high-severity Missing Authorization vulnerability in the FundEngine WordPress plugin, affecting versions <= 1.7.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.7.1; sites on affected versions should update now. Disclosed July 2024, reported by Thanh Nam Tran.

Vulnerability Overview

The FundEngine plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.7.0. This is due to the plugin not properly verifying user meta updated through the update_user_meta function. This makes it possible for authenticated attackers, with subscriber-level access and above, to update their user meta which can be leveraged to update their capabilities to gain administrator access.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in FundEngine <= 1.7.0 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 FundEngine the fix is 1.7.1: builds <= 1.7.0 are affected, anything from 1.7.1 onward is not.

Remediation

Update to version 1.7.1, 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: FundEngine 1.7.1 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