CVE-2024-6551

GiveWP <= 3.15.1 - Unauthenticated Full Path Disclosure

2024-08-28 00:00
stealthcopter

Strategic Overview

Status
Patched in 3.16.0
Affected Plugin
GiveWP – Donation Plugin and Fundraising Platform
Affected Version
<= 3.15.1
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-6551
View all GiveWP – Donation Plugin and Fundraising Platform vulnerabilities

At a glance

CVE-2024-6551 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the GiveWP WordPress plugin, affecting versions <= 3.15.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.16.0; sites on affected versions should update now. Disclosed August 2024, reported by stealthcopter.

Vulnerability Overview

The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.15.1. This is due to the plugin utilizing Symfony and leaving display_errors on within test files. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in GiveWP <= 3.15.1 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For GiveWP the fix is 3.16.0: builds <= 3.15.1 are affected, anything from 3.16.0 onward is not.

Remediation

Update to version 3.16.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: GiveWP 3.16.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-6551https://www.wordfence.com/threat-intel/vulnerabilities/id/2a13ce09-b312-4186-b0e2-63065c47f15dhttps://nvd.nist.gov/vuln/detail/CVE-2024-6551

Related records

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