CVE-2026-7619: SQL Injection in Charitable WordPress Plugin
Platform
wordpress
Component
charitable
Fixed in
1.8.10.5
CVE-2026-7619 describes a SQL Injection vulnerability discovered in the Charitable WordPress plugin, a popular tool for fundraising and recurring donations. This flaw allows authenticated attackers to inject arbitrary SQL queries, potentially leading to data breaches and compromise of the WordPress site. The vulnerability affects versions 1.0.0 through 1.8.10.4, and a patch is available in version 1.8.10.5.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Impact and Attack Scenarios
Successful exploitation of CVE-2026-7619 could allow an attacker to extract sensitive data stored within the WordPress database. This includes donor information (names, addresses, payment details), donation amounts, and potentially user credentials. The attacker would need to be an authenticated user with the 'editothersdonations' capability or higher, typically an administrator or editor. While the vulnerability requires authentication, the widespread use of WordPress and the plugin's popularity make it a potentially significant risk. A successful attack could lead to financial loss for the organization, reputational damage, and regulatory penalties due to data breaches.
Exploitation Context
CVE-2026-7619 was published on 2026-05-13. Its severity is currently assessed as medium. There is no indication of this vulnerability being actively exploited in the wild, nor is it currently listed on KEV or EPSS. Public proof-of-concept (POC) code is not widely available, which may limit immediate exploitation. Monitor security advisories and threat intelligence feeds for any changes in the exploitation landscape.
Threat Intelligence
Exploit Status
CISA SSVC
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- Low — any valid user account is sufficient. Basic authenticated access required.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
- Integrity
- None — no integrity impact. Attacker cannot modify data.
- Availability
- None — no availability impact. Service remains fully operational.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
Mitigation and Workarounds
The primary mitigation for CVE-2026-7619 is to immediately upgrade the Charitable WordPress plugin to version 1.8.10.5 or later. If an immediate upgrade is not possible due to compatibility issues or testing requirements, consider implementing a Web Application Firewall (WAF) rule to filter potentially malicious SQL injection attempts targeting the 's' parameter. Specifically, look for unusual characters or SQL keywords in the parameter value. Additionally, review WordPress user roles and permissions to ensure that only authorized personnel have access to the donation management admin area. After upgrading, verify the fix by attempting a SQL injection attack on the vulnerable parameter and confirming that the attack is blocked.
How to fix
Update to version 1.8.10.5, or a newer patched version
Frequently asked questions
What is CVE-2026-7619 — SQL Injection in Charitable WordPress Plugin?
CVE-2026-7619 is a SQL Injection vulnerability affecting the Charitable WordPress plugin versions 1.0.0–1.8.10.4. It allows authenticated attackers to inject malicious SQL queries, potentially extracting sensitive data.
Am I affected by CVE-2026-7619 in Charitable WordPress Plugin?
You are affected if you are using the Charitable WordPress plugin in versions 1.0.0 through 1.8.10.4. Check your plugin version and upgrade immediately if vulnerable.
How do I fix CVE-2026-7619 in Charitable WordPress Plugin?
Upgrade the Charitable WordPress plugin to version 1.8.10.5 or later. As a temporary workaround, implement a WAF rule to filter malicious SQL injection attempts.
Is CVE-2026-7619 being actively exploited?
There is currently no public evidence of CVE-2026-7619 being actively exploited in the wild, but it's crucial to apply the patch promptly to mitigate the risk.
Where can I find the official Charitable WordPress advisory for CVE-2026-7619?
Refer to the official Charitable WordPress plugin website and WordPress.org plugin repository for the latest security advisory and update information regarding CVE-2026-7619.
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Scan your WordPress project now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...