Wp WhydonateWordPress extension · Whydonate
CVE-2023-29238
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 Whydonate Whydonate – FREE Donate button – Crowdfunding – Fundraising plugin <= 3.12.15 versions.
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 Whydonate WordPress donation plugin affecting versions 3.12.15 and below. The vulnerability allows attackers to trick authenticated administrators or users into performing unintended actions (such as modifying donation settings, creating campaigns, or changing user permissions) by crafting malicious requests that the victim's browser automatically submits.
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
Wp WhydonateWordPress extension
<= 3.12.15CVSS 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.
-
Verify Whydonate plugin is installedAccess WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Whydonate' or check the plugin directory /wp-content/plugins/whydonate/ for the plugin filesAffected if The Whydonate plugin is found in the WordPress installation
-
Check Whydonate plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Whydonate, and note the version number displayed; alternatively, open /wp-content/plugins/whydonate/whydonate.php and check the 'Version' field in the plugin header commentAffected if The installed version is 3.12.15 or lower
-
Confirm plugin is activeIn Plugins > Installed Plugins, verify the Whydonate plugin shows as 'Active' under the status columnAffected if The plugin is active and the version is <= 3.12.15
-
Inspect plugin for missing nonce verification (optional)Examine the main plugin PHP files for form submissions and AJAX actions - search for instances where wp_nonce_field, wp_verify_nonce, or check_admin_referer are NOT used before processing requestsAffected if Forms or AJAX handlers in the plugin code lack CSRF nonce verification and the plugin version is <= 3.12.15
A WordPress site is affected if the Whydonate plugin version 3.12.15 or lower is installed and active, with forms or AJAX actions missing anti-CSRF nonce validation.
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.
From vendor dataUpdate the Whydonate plugin to a version newer than 3.12.15. If no update is available, manually add anti-CSRF nonce tokens to all forms and AJAX actions, and validate those nonces on the server side.
Fix this in Wp Whydonate
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29238 — 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-2023-29238 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