dbcve.org
GivewpWordPress extension

CVE-2024-6551

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 3.16.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GiveWP WordPress donation plugin is vulnerable to Full Path Disclosure due to Symfony test files left in production with PHP's display_errors enabled. Unauthenticated attackers can request these test files to reveal the server's full filesystem path, which aids in reconnaissance but requires another vulnerability to cause actual damage.

MitigationDisable display_errors in PHP configuration (php.ini or .htaccess), and update GiveWP to version 3.15.2 or later which removes the vulnerable test files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GivewpWordPress extension
Affected:< 3.16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GiveWP plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the GiveWP entry to see its version number. Alternatively, check the version listed in the plugin's main PHP file header.
    Affected if The installed version is below 3.16.0 (any version from 2.0 through 3.15.x is vulnerable)
  2. Verify PHP display_errors setting
    Check your php.ini file for 'display_errors = On' or run 'php -i | grep display_errors' from command line. You can also check via WordPress debug logs or by creating a PHP info page.
    Affected if display_errors is set to On (On means the vulnerability can be exploited; Off mitigates it)
  3. Locate Symfony test files in GiveWP directory
    Search the wp-content/plugins/give directory for files containing 'test' or 'Test' in the filename, particularly looking in vendor/symfony or similar test directories. Common test file patterns include anything.php, *_test.php, or Test.php.
    Affected if Any Symfony or PHPUnit test files remain in the production plugin directory (vulnerable versions ship with these files)
  4. Confirm web accessibility of test files
    Attempt to access known test file paths via HTTP request (e.g., request any .php file with 'test' in the name found in the previous step). Check the HTTP response for full filesystem path disclosure.
    Affected if Requesting test files returns full server paths in error messages (this confirms active exploitation potential)

You are affected if GiveWP version is below 3.16.0 AND PHP display_errors is enabled AND test files are present and web-accessible, as all three conditions must exist for the full path disclosure to work.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.16.0 or later
Fixed in 3.16.0
Interim mitigation

Disable display_errors in PHP configuration (php.ini or .htaccess), and update GiveWP to version 3.15.2 or later which removes the vulnerable test files.

Recommended fix High confidence

GiveWP version 3.16.0

  1. Backup your WordPress site and database before making any changes
  2. Update the GiveWP plugin to version 3.16.0 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. Alternatively, update via FTP/SFTP by uploading the new plugin files to wp-content/plugins/give
  4. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  5. Clear any cache if your site uses caching plugins or server-side caching
  6. Test the donation functionality to ensure the plugin is working correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Givewp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6551 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6551 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data