Donations Made Easy Smart DonationsWordPress extension · Rednao
CVE-2023-47550
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 RedNao Donations Made Easy – Smart Donations allows Stored XSS.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 confidenceA CSRF vulnerability in the Donations Made Easy – Smart Donations WordPress plugin (versions up to 4.0.12) allows attackers to trick authenticated administrators into submitting malicious requests that inject and persistently store XSS payloads into donation forms or plugin settings.
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
<= 4.0.12CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Smart Donations plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Rednao Donations Made Easy - Smart Donations' or 'Smart Donations'Affected if plugin is present in the WordPress installation
-
Check installed plugin versionIn Plugins page, click 'View Details' on the Smart Donations plugin to see the version numberAffected if version is 4.0.12 or lower
-
Inspect donation form configurations for suspicious scriptsNavigate to Smart Donations settings (usually under Donations or Smart Donations menu) and examine any customizable fields in donation forms (form title, descriptions, button labels, custom fields) for injected JavaScript or HTML tags like <script>, <img onerror=, or javascript:Affected if any donation form or setting contains unexpected script tags or event handlers
-
Review plugin database for stored XSS payloadsAccess WordPress database via phpMyAdmin or CLI and query the options table for Smart Donations related settings: SELECT * FROM wp_options WHERE option_name LIKE '%smartdonations%' OR option_name LIKE '%rednao%donation%'; Examine stored values for encoded or raw XSS patternsAffected if database contains unexpected HTML, script tags, or event handlers in plugin settings
You are affected if the Smart Donations plugin is installed at version 4.0.12 or lower and either donation form configurations or the database contain injected XSS payloads from CSRF-triggered requests.
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 dataImplement anti-CSRF tokens (nonces) on all plugin forms and admin actions, combined with proper input sanitization and output encoding to prevent Stored XSS. Until a patch is available, restrict admin access and monitor for suspicious form submissions.
Fix this in Donations Made Easy Smart Donations
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47550 — 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-47550 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