GivewpWordPress extension
CVE-2024-47315
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in StellarWP GiveWP give.This issue affects GiveWP: from n/a through <= 3.15.1.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the GiveWP WordPress donation plugin. Attackers can trick authenticated administrators into unknowingly executing unintended actions (such as modifying donation settings, creating or processing donations, or altering campaign configurations) by luring them to visit malicious pages that make forged requests to the vulnerable site.
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
< 3.16.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check GiveWP installed versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins, locate GiveWP, and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/givewp/plugin.php or via WP-CLI: wp plugin list | grep giveAffected if The installed version is lower than 3.16.0 (e.g., 3.15.2, 3.14.1, etc.)
-
Verify nonce implementation in form handlersExamine the main GiveWP plugin files (particularly in includes/ directory) for state-changing form submissions (donation forms, settings forms, campaign forms). Search for add_action() calls handling POST/GET requests and check if they include wp_verify_nonce() or check_admin_referer() calls. Look for missing nonce verification around donation creation, settings updates, and campaign modifications.Affected if State-changing form handlers lack nonce verification or use wp_verify_nonce() incorrectly (e.g., no nonce field in the form, or nonce not validated before processing)
-
Inspect AJAX endpoint nonce validationReview AJAX action handlers in GiveWP (hooks like wp_ajax_give_* and wp_ajax_nopriv_give_*) and verify each calls wp_verify_nonce() or check_ajax_referer() before processing. Check files in includes/ajax.php or similar locations.Affected if AJAX endpoints that modify data (create donation, update settings, process campaigns) do not validate nonces
-
Check for Origin/Referer header validationSearch plugin code for $_SERVER['HTTP_ORIGIN'], $_SERVER['HTTP_REFERER'] checks or server-side origin validation in the main request handling files. Look for code that validates request source before processing state-changing operations.Affected if No server-side validation of Origin or Referer headers exists to ensure requests come from legitimate sources
You are affected if GiveWP version is below 3.16.0 AND the plugin lacks proper nonce validation on form submissions and AJAX endpoints handling donation and configuration changes.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.16.0
Implement anti-CSRF tokens (nonces) on all state-changing form submissions and AJAX endpoints within GiveWP, and validate the Origin/Referer headers server-side to ensure requests originate from legitimate sources.
GiveWP 3.16.0
- Backup your WordPress site and database before making any changes
- Update the GiveWP plugin to version 3.16.0 or later through the WordPress admin dashboard (Plugins > Add New > Upload or WordPress updates)
- Alternatively, update via WP-CLI: wp plugin update give
- After updating, verify the plugin version shows 3.16.0 or higher in Plugins > Installed Plugins
- Test critical donation workflows to ensure the plugin functions 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
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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