dbcve.org
Donations Made Easy Smart DonationsWordPress extension · Rednao

CVE-2023-47551

HIGH · 8.8 CVSS v3.1 Published 2023-11-18
Fix available
A fix is available. Upgrade to after 4.0.12 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in RedNao Donations Made Easy – Smart Donations.This issue affects Donations Made Easy – Smart Donations: from n/a through 4.0.12.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the RedNao Donations Made Easy – Smart Donations WordPress plugin (versions through 4.0.12). The plugin lacks proper anti-CSRF token validation on state-changing actions, allowing attackers to trick authenticated administrators into unknowingly performing unauthorized donation-related operations.

MitigationImplement anti-CSRF tokens (nonce validation) for all form submissions and AJAX actions that modify plugin state, and ensure the WordPress nonces are validated on the server side before processing any requests.

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
Donations Made Easy Smart DonationsWordPress extension
Affected:<= 4.0.12

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
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 checks

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

  1. Verify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find 'RedNao Donations Made Easy - Smart Donations'. Note the version number displayed, or check the plugin's main PHP file (usually smart-donations.php) for the Version header comment.
    Affected if The plugin is installed and the version is 4.0.12 or lower.
  2. Locate plugin state-changing handlers
    Access the plugin directory via file manager or FTP at wp-content/plugins/smart-donations/. Identify PHP files that handle form submissions, AJAX requests, or URL actions that modify donation data (look for functions handling donation creation, modification, deletion, or settings updates).
    Affected if The plugin is present and processes donation-related actions through PHP handlers.
  3. Inspect form handlers for nonce validation
    Open the identified state-changing PHP files and search for the presence of WordPress nonce verification functions: 'wp_verify_nonce', 'check_admin_referer', 'check_ajax_referer', or 'wp_nonce_field' in form definitions. Also check for 'nonce' or '_wpnonce' in the code.
    Affected if These nonce validation functions are absent or not used before processing state-changing operations, indicating vulnerability to CSRF.
  4. Verify plugin exposes donation management interfaces
    Check if the plugin provides admin pages under /wp-admin/ that allow managing donations, creating donation forms, or modifying settings. These would be the targets for CSRF attacks.
    Affected if The plugin exposes administrative interfaces for donation management accessible to authenticated administrators.

You are affected if the Smart Donations plugin version is 4.0.12 or lower AND the plugin processes state-changing donation actions without validating WordPress nonces.

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.

From vendor data
Upgrade available Upgrade to a release after 4.0.12
Interim mitigation

Implement anti-CSRF tokens (nonce validation) for all form submissions and AJAX actions that modify plugin state, and ensure the WordPress nonces are validated on the server side before processing any requests.

Fix this in Donations Made Easy Smart Donations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47551 — 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-2023-47551 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