CVE-2025-11893 identifies a critical SQL Injection vulnerability in the Charitable – Donation Plugin for WordPress, specifically in the handling of the donation_ids parameter. The vulnerability arises from improper neutralization of special elements in SQL commands (CWE-89), where user-supplied input is insufficiently escaped and the SQL query is not properly prepared, allowing attackers to append arbitrary SQL code. The flaw affects all plugin versions up to and including 1.8.8.4. Exploitation requires an attacker to be authenticated with at least Subscriber-level privileges and to have made a paid donation, which provides a vector to manipulate the donation_ids parameter. Successful exploitation can lead to extraction of sensitive database information, modification of data, or disruption of service. The CVSS 3.1 base score is 8.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and no user interaction needed beyond authentication. No known public exploits have been reported yet, but the vulnerability poses a significant risk to WordPress sites using this plugin for fundraising and recurring donations. The plugin is widely used by nonprofits and charitable organizations to manage donations, making this vulnerability particularly concerning for entities relying on it for financial operations and donor data management.

For European organizations, this vulnerability could lead to severe data breaches involving donor information, financial records, and potentially other sensitive data stored in the WordPress database. The ability to execute arbitrary SQL queries can compromise the integrity of donation records, disrupt fundraising operations, and damage organizational reputation. Nonprofits and charities that rely heavily on this plugin for recurring donations are at risk of financial fraud or data leakage. Additionally, the disruption of donation processing could impact cash flow and operational continuity. Given the high adoption of WordPress in Europe and the active nonprofit sector, the impact could be widespread, affecting organizations that manage donor trust and comply with strict data protection regulations such as GDPR. The requirement for authenticated access with a paid donation limits the attack surface but does not eliminate risk, especially if subscriber accounts are compromised or created fraudulently.

1. Monitor for and apply plugin updates immediately once a patch is released by the vendor to address this vulnerability. 2. Restrict Subscriber-level permissions to the minimum necessary and audit accounts with donation capabilities to prevent unauthorized access. 3. Implement Web Application Firewalls (WAFs) with SQL Injection detection and prevention rules tailored to WordPress and this plugin's typical query patterns. 4. Conduct regular security audits and database activity monitoring to detect anomalous queries or data access patterns related to donation_ids. 5. Enforce strong authentication mechanisms and monitor for suspicious login activity to reduce the risk of account compromise. 6. Consider temporarily disabling the plugin or donation features if a patch is not yet available and the risk is deemed high. 7. Educate staff and users about the risks of account sharing and phishing that could lead to unauthorized authenticated access. 8. Backup databases frequently and verify backup integrity to enable recovery in case of data tampering or loss.