dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-7619

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More plugin for WordPress is vulnerable to generic SQL Injection via the 's' parameter in all versions up to, and including, 1.8.10.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 access to the donation management admin area (requiring the edit_others_donations capability) and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 confidence

The Charitable WordPress donation plugin versions up to 1.8.10.4 contain a SQL injection vulnerability in the search functionality via the 's' parameter. The flaw stems from insufficient input sanitization combined with a lack of prepared statements in the SQL query, allowing authenticated attackers with edit_others_donations capability to inject arbitrary SQL commands and extract sensitive database information.

MitigationUpdate the Charitable plugin to version 1.8.10.5 or later. If no update is available, implement proper escaping using $wpdb->prepare() for the 's' parameter and ensure all SQL queries use prepared statements.

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 checks

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

  1. Check installed Charitable plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Charitable. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/charitable/charitable.php for 'Version:' value.
    Affected if Version is 1.8.10.4 or lower (any version up to and including 1.8.10.4)
  2. Confirm plugin handles donation searches
    Navigate to the Charitable donations list view in wp-admin (usually Donations > Donations). Look for a search input field that accepts a 's' parameter in the URL when used.
    Affected if The search functionality with 's' parameter exists and is accessible to authenticated users
  3. Verify user has edit_others_donations capability
    Check the WordPress user role or capability assigned to the account. In wp-admin, go to Users > Your Profile to view capabilities, or query the wp_usermeta table for 'wp_capabilities' meta_value containing 'edit_others_donations'.
    Affected if The logged-in user or their role includes the edit_others_donations capability
  4. Test SQL injection via search parameter
    If authenticated with the required capability, perform a test search using the 's' parameter with a harmless SQL payload such as "test' AND 1=1--" appended to the search query. Monitor for SQL errors or unexpected database behavior.
    Affected if The search returns data without proper escaping or throws SQL syntax errors, indicating unsanitized input is processed

You are affected if the Charitable plugin version is 1.8.10.4 or lower AND the search functionality using the 's' parameter is accessible to a user account with edit_others_donations capability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Charitable plugin to version 1.8.10.5 or later. If no update is available, implement proper escaping using $wpdb->prepare() for the 's' parameter and ensure all SQL queries use prepared statements.

Recommended fix Moderate confidence

Upgrade Charitable plugin to version 1.8.11 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Charitable – Donation Plugin for WordPress' plugin
  4. 4. Check the current version number (if installed version is 1.8.10.4 or earlier, the site is vulnerable)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/charitable/ and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is running version 1.8.11 or higher
Caveat Review plugin changelog for any breaking changes between your current version and the new version before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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