Smart DonationsWordPress extension · Rednao
CVE-2023-40664
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in RedNao Donations Made Easy – Smart Donations plugin <= 4.0.12 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 · high confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the RedNao Donations Made Easy – Smart Donations WordPress plugin versions 4.0.12 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that is reflected back in the application's response without proper output encoding.
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
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.
-
Confirm WordPress installationVerify that the website is running WordPress by checking for the presence of wp-config.php or the wp-admin login pageAffected if WordPress is not present - this CVE does not apply
-
Verify Smart Donations plugin is installedCheck for the presence of the Smart Donations plugin in wp-content/plugins/ or list installed plugins via WordPress admin under PluginsAffected if The Smart Donations plugin is not installed - this CVE does not apply
-
Identify installed plugin versionCheck the plugin version in the plugin header comment within the main plugin PHP file (e.g., smart-donations.php) or view the version displayed in WordPress admin under Plugins > Smart DonationsAffected if Version is 4.0.12 or lower - the environment is vulnerable to CVE-2023-40664
-
Assess exposure to reflected XSSThe vulnerability is an unauthenticated reflected XSS affecting the plugin. If the plugin is active and version is <= 4.0.12, attacker can inject malicious JavaScript through unsanitized user input that gets reflected in the response without output encodingAffected if Plugin is active and version <= 4.0.12 - the environment is affected by this CVE
The environment is affected if the Smart Donations (Rednao Smart Donations) plugin is installed with a version of 4.0.12 or lower.
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 dataUpgrade the Smart Donations plugin to version 4.0.13 or later, which contains the security patch. Until then, implement Web Application Firewall (WAF) rules to block XSS attack patterns and warn users not to click untrusted links.
Fix this in Smart Donations
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40664 — 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-40664 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