CVE-2024-5977

GiveWP – Donation Plugin and Fundraising Platform <= 3.13.0 - Insecure Direct Object Reference to Authenticated (GiveWP Worker+) Arbitrary Post Actions

2024-07-18 00:00
Thanh Nam Tran

Strategic Overview

Status
Patched in 3.14.0
Affected Plugin
GiveWP – Donation Plugin and Fundraising Platform
Affected Version
<= 3.13.0
CVSS
5.4Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-5977
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

CVE-2024-5977 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the GiveWP WordPress plugin, affecting versions <= 3.13.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at GiveWP Worker level or above. The issue is fixed in version 3.14.0; sites on affected versions should update now. Disclosed July 2024, reported by Thanh Nam Tran.

Vulnerability Overview

The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.13.0 via the 'handleRequest' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with GiveWP Worker-level access and above, to delete and update arbitrary posts.

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

GiveWP <= 3.13.0 carries this weakness at handleRequest, and reaching it takes an account at GiveWP Worker 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 GiveWP the fix is 3.14.0: builds <= 3.13.0 are affected, anything from 3.14.0 onward is not.

Remediation

Update to version 3.14.0, 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: GiveWP 3.14.0 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-5977https://www.wordfence.com/threat-intel/vulnerabilities/id/2dca6c29-9f05-4d82-90e3-834f1dd8005ahttps://nvd.nist.gov/vuln/detail/CVE-2024-5977

Related records

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