CVE-2025-11893
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 · uneditedThe Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More plugin for WordPress is vulnerable to SQL Injection via the donation_ids parameter in all versions up to, and including, 1.8.8.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation of the vulnerability requires a paid donation.
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 confidenceThe Charitable WordPress plugin up to version 1.8.8.4 contains an authenticated SQL injection vulnerability in the donation_ids parameter. The plugin fails to properly escape user input and does not use prepared statements when querying the database, allowing authenticated attackers with Subscriber-level access to inject arbitrary SQL commands. Exploitation requires the attacker to have made a paid donation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check Charitable plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Charitable. The version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., /wp-content/plugins/charitable/include/class-charitable.php) for the 'Version' header in the file comments.Affected if The installed version is 1.8.8.4 or lower.
-
Verify donation_ids parameter is accessibleExamine the PHP code handling the donation_ids parameter in the plugin, typically in AJAX handlers or form processing files. Look for endpoints that accept this parameter without proper sanitization.Affected if The donation_ids parameter is processed without sanitization or prepared statements.
-
Check for SQL query preparationSearch the plugin codebase for queries using the donation_ids parameter. Look for $wpdb->prepare() usage with proper placeholder substitution ($wpdb->prepare('%d', $donation_ids) or similar).Affected if Queries using donation_ids do not use $wpdb->prepare() with parameterized queries.
-
Confirm user role accessReview the plugin to confirm that Subscriber-level users who have made a paid donation can access the vulnerable endpoint.Affected if Authenticated users with Subscriber role and a paid donation history can trigger the vulnerable code path.
A user is affected if the Charitable plugin version is 1.8.8.4 or lower and the donation_ids parameter endpoint is accessible to authenticated subscribers with paid donations.
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 · scopedUpgrade to the latest version of the Charitable plugin and ensure all SQL queries use $wpdb->prepare() with proper placeholder substitution. Review other donation-related endpoints for similar injection vulnerabilities.
Charitable plugin version 1.8.8.5 or higher
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the Charitable plugin and click Update now (or update all plugins)
- Alternatively, run: wp plugin update charitable
- Verify the updated version is 1.8.8.5 or higher after update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11893 — 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-2025-11893 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