HomeWordPress vulnerabilitiesGiveWP
GiveWP vulnerabilities
GiveWP has 54 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 54
- Active installs
- 100,000+
- Latest version
- 4.17.0
- Last updated
- 23 Sep 2026
- Most recent
- 6 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-104672 | High 7.1 | Up to 4.17.0 | No fixed version yet | 1 d ago |
| Privilege escalation CVE-2026-104405 | High 8.1 | Up to 4.17.0 | No fixed version yet | 1 d ago |
| Cross-site scripting (XSS) CVE-2026-104404 | Medium 6.5 | Up to 4.17.0 | No fixed version yet | 2 d ago |
| Security weakness CVE-2026-85113 | Medium 6.5 | Before 4.16.9 | Fixed in 4.16.9 | 21 Sep 2026 |
| Privilege escalation CVE-2026-85530 | High 8.1 | Before 4.16.8.1 | Fixed in 4.16.8.1 | 16 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-5510 | Medium 6.4 | Up to 4.14.4 | Fixed in a later version (latest 4.17.0) | 28 Aug 2026 |
| Broken access control CVE-2026-14317 | Medium 5.3 | Before 4.16.3 | Fixed in 4.16.3 | 31 Jul 2026 |
| Sensitive data exposure CVE-2026-14319 | High 7.5 | Before 4.16.3 | Fixed in 4.16.3 | 31 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-14318 | Medium 6.8 | Before 4.16.3 | Fixed in 4.16.3 | 30 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-14987 | Medium 6.4 | Up to 4.16.3 | Fixed in a later version (latest 4.17.0) | 16 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-13704 | Medium 6.4 | Up to 4.16.1 | Fixed in a later version (latest 4.17.0) | 2 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-13246 | Medium 6.4 | Up to 4.16.0 | Fixed in a later version (latest 4.17.0) | 1 Jul 2026 |
| Cross-site request forgery (CSRF) CVE-2026-11981 | Medium 4.3 | Up to 4.15.3 | Fixed in a later version (latest 4.17.0) | 1 Jul 2026 |
| Cross-site scripting (XSS) CVE-2025-13206 | High 7.2 | Before 4.13.1 | Fixed in 4.13.1 | 19 Nov 2025 |
| Broken access control CVE-2025-11228 | Medium 5.3 | Before 4.10.1 | Fixed in 4.10.1 | 4 Oct 2025 |
| Broken access control CVE-2025-11227 | Medium 6.5 | Before 4.10.1 | Fixed in 4.10.1 | 4 Oct 2025 |
| Broken access control CVE-2025-7221 | Medium 4.3 | Before 4.6.1 | Fixed in 4.6.1 | 21 Aug 2025 |
| Sensitive data exposure CVE-2025-8620 | Medium 5.3 | Before 4.6.1 | Fixed in 4.6.1 | 6 Aug 2025 |
| Cross-site scripting (XSS) CVE-2025-7205 | Medium 5.4 | Before 4.6.0 | Fixed in 4.6.0 | 31 Jul 2025 |
| Broken access control CVE-2025-4571 | Medium 5.4 | Before 4.3.1 | Fixed in 4.3.1 | 19 Jun 2025 |
| Sensitive data exposure CVE-2025-2331 | Medium 5.3 | Before 3.22.2 | Fixed in 3.22.2 | 22 Mar 2025 |
| Broken access control CVE-2025-2025 | Medium 6.5 | Before 3.22.1 | Fixed in 3.22.1 | 15 Mar 2025 |
| Remote code execution CVE-2025-0912 | Critical 9.8 | Before 3.20.0 | Fixed in 3.20.0 | 4 Mar 2025 |
| Remote code execution CVE-2024-12877 | Critical 9.8 | Up to 3.19.2 | Fixed in a later version (latest 4.17.0) | 11 Jan 2025 |
| Cross-site scripting (XSS) CVE-2024-11921 | Medium 4.8 | Before 3.19.0 | Fixed in 3.19.0 | 27 Dec 2024 |
| Remote code execution CVE-2024-9634 | Critical 9.8 | Before 3.16.4 | Fixed in 3.16.4 | 16 Oct 2024 |
| Remote code execution CVE-2024-8353 | Critical 9.8 | Before 3.16.2 | Fixed in 3.16.2 | 28 Sep 2024 |
| SQL injection CVE-2024-9130 | High 7.2 | Before 3.16.2 | Fixed in 3.16.2 | 27 Sep 2024 |
| Sensitive data exposure CVE-2024-6551 | Medium 5.3 | Before 3.16.0 | Fixed in 3.16.0 | 29 Aug 2024 |
| Broken access control CVE-2024-5941 | Medium 5.4 | Before 3.14.2 | Fixed in 3.14.2 | 20 Aug 2024 |
| PHP object injection CVE-2024-5932 | Critical 10.0 | Before 3.14.2 | Fixed in 3.14.2 | 20 Aug 2024 |
| Broken access control CVE-2024-5939 | Medium 5.3 | Before 3.14.0 | Fixed in 3.14.0 | 20 Aug 2024 |
| Broken access control CVE-2024-5940 | Medium 6.5 | Before 3.14.0 | Fixed in 3.14.0 | 20 Aug 2024 |
| Broken access control CVE-2024-5977 | Medium 5.4 | Before 3.14.0 | Fixed in 3.14.0 | 19 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-3714 | Medium 6.4 | Before 3.11.0 | Fixed in 3.11.0 | 18 May 2024 |
| Cross-site scripting (XSS) CVE-2024-1957 | Medium 6.4 | Before 3.7.0 | Fixed in 3.7.0 | 13 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-1424 | Medium 6.4 | Before 3.6.0 | Fixed in 3.6.0 | 9 Apr 2024 |
| SQL injection CVE-2023-0224 | Critical 9.8 | Before 2.24.1 | Fixed in 2.24.1 | 16 Jan 2024 |
| Cross-site request forgery (CSRF) CVE-2023-4246 | Medium 4.3 | Up to 2.33.3 | Fixed in a later version (latest 4.17.0) | 11 Jan 2024 |
| Cross-site request forgery (CSRF) CVE-2023-4247 | Medium 5.4 | Up to 2.33.3 | Fixed in a later version (latest 4.17.0) | 11 Jan 2024 |
| Cross-site request forgery (CSRF) CVE-2023-4248 | Medium 5.4 | Up to 2.33.3 | Fixed in a later version (latest 4.17.0) | 11 Jan 2024 |
| Cross-site scripting (XSS) CVE-2022-4448 | Medium 5.4 | Before 2.24.0 | Fixed in 2.24.0 | 13 Feb 2023 |
| Cross-site scripting (XSS) CVE-2022-2215 | Medium 4.8 | Before 2.21.3 | Fixed in 2.21.3 | 1 Aug 2022 |
| Cross-site request forgery (CSRF) CVE-2022-2260 | Medium 6.5 | Before 2.21.3 | Fixed in 2.21.3 | 1 Aug 2022 |
| Arbitrary file upload CVE-2022-28700 | Critical 9.1 | Before 2.21.0 | Fixed in 2.21.0 | 21 Jul 2022 |
| Arbitrary file read CVE-2022-31475 | Medium 5.5 | Before 2.21.0 | Fixed in 2.21.0 | 21 Jul 2022 |
| Sensitive data exposure CVE-2022-2117 | Medium 5.3 | Up to 2.20.2 | Fixed in a later version (latest 4.17.0) | 18 Jul 2022 |
| Cross-site scripting (XSS) CVE-2022-0252 | Medium 6.1 | Before 2.17.3 | Fixed in 2.17.3 | 21 Feb 2022 |
| Cross-site scripting (XSS) CVE-2021-25099 | Medium 6.1 | Before 2.17.3 | Fixed in 2.17.3 | 21 Feb 2022 |
| Cross-site scripting (XSS) CVE-2021-25100 | Medium 6.1 | Before 2.17.3 | Fixed in 2.17.3 | 21 Feb 2022 |
| Cross-site scripting (XSS) CVE-2021-24524 | Medium 4.8 | Before 2.12.0 | Fixed in 2.12.0 | 23 Aug 2021 |
| Cross-site scripting (XSS) CVE-2021-24315 | Medium 4.8 | Before 2.10.4 | Fixed in 2.10.4 | 17 May 2021 |
| Cross-site scripting (XSS) CVE-2021-24213 | Medium 6.1 | Before 2.10.0 | Fixed in 2.10.0 | 12 Apr 2021 |
| Cross-site scripting (XSS) CVE-2019-15317 | Medium 5.4 | Before 2.4.7 | Fixed in 2.4.7 | 22 Aug 2019 |
Read the published descriptions
- CVE-2026-104672, 6 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in GiveWP <= 4.17.0 versions. CVE record
- CVE-2026-104405, 6 Oct 2026
- Unauthenticated Privilege Escalation in GiveWP <= 4.17.0 versions. CVE record
- CVE-2026-104404, 5 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP GiveWP give allows Stored XSS.This issue affects GiveWP: from n/a through 4.17.0. CVE record
- CVE-2026-85113, 21 Sep 2026
- The GiveWP WordPress plugin before 4.16.9 does not remove shortcode delimiters from donor-supplied values before rendering them on public pages, and the shortcode stripping it applies can be defeated by nesting, allowing unauthenticated users to execute arbitrary shortcodes registered on the site. CVE record
- CVE-2026-85530, 16 Sep 2026
- The GiveWP WordPress plugin before 4.16.8.1 does not consistently normalise a donor's e-mail address between the value it stores and the value it later uses to look that donor up, allowing unauthenticated users to be resolved as an arbitrary donor and to set the WordPress password of any user account linked to one, including an administrator's. CVE record
- CVE-2026-5510, 28 Aug 2026
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'give_form' shortcode in all versions up to, and including, 4.14.4. This is due to insufficient input sanitization and output escaping on the continue_button_title and display_style shortcode attributes, which are passed through sanitize_text_field() but not properly escaped when output in HTML data attributes. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-14317, 31 Jul 2026
- The GiveWP WordPress plugin before 4.16.3 does not restrict the set of available payment gateways to those enabled by the administrator, deriving it in part from request input, which allows unauthenticated users to complete donations through a payment gateway the administrator has disabled. CVE record
- CVE-2026-14319, 31 Jul 2026
- The GiveWP WordPress plugin before 4.16.3 does not properly restrict access to a REST API endpoint that returns recurring-donation records, allowing unauthenticated users to retrieve information about anonymous recurring donors, including their name and subscription details. CVE record
- CVE-2026-14318, 30 Jul 2026
- The GiveWP WordPress plugin before 4.16.3 does not escape a donation-form template setting before outputting it in an HTML attribute, allowing users with the GiveWP Worker role and above to inject arbitrary web scripts that execute on the public donation form viewed by any visitor. CVE record
- CVE-2026-14987, 16 Jul 2026
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'twitter_message' Sequoia Template Setting in all versions up to, and including, 4.16.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with give worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected script executes specifically when a donor clicks the Share on Twitter button on the Sequoia donation confirmation view, as that is when the unescaped twitter_message value is evaluated inside the JavaScript template literal. CVE record
- CVE-2026-13704, 2 Jul 2026
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sequoia[introduction][image]' parameter in all versions up to, and including, 4.16.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Give Worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-13246, 1 Jul 2026
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'block_id' (and other) shortcode attributes of the 'givewp_campaign_comments' shortcode in versions up to, and including, 4.16.0. This is due to insufficient input sanitization and output escaping on user supplied attributes in CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render(), where the blockId value is interpolated directly into a single-quoted HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-11981, 1 Jul 2026
- The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.15.3 This is due to missing nonce validation on the give_set_notification_status_handler() function. This makes it possible for unauthenticated attackers to disable donation email notifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2025-13206, 19 Nov 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘name’ parameter in all versions up to, and including, 4.13.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Avatars must be enabled in the WordPress install in order to exploit the vulnerability. CVE record
- CVE-2025-11228, 4 Oct 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `registerAssociateFormsWithCampaign` function in all versions up to, and including, 4.10.0. This makes it possible for unauthenticated attackers to associate any donation forms with any campaign. CVE record
- CVE-2025-11227, 4 Oct 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.10.0 via the 'registerGetForm', 'registerGetForms', 'registerGetCampaign' and 'registerGetCampaigns' functions due to a missing capability check. This makes it possible for unauthenticated attackers to extract data from private and draft donation forms, as well as archived campaigns. CVE record
- CVE-2025-7221, 21 Aug 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the give_update_payment_status() function in all versions up to, and including, 4.5.0. This makes it possible for authenticated attackers, with GiveWP Worker-level access and above, to update donations statuses. This ability is not present in the user interface. CVE record
- CVE-2025-8620, 6 Aug 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 4.6.0. This makes it possible for unauthenticated attackers to extract donor names, emails, and donor id. CVE-2025-47444 is a duplicate of this issue. CVE-2025-47444 is a duplicate of this issue. CVE record
- CVE-2025-7205, 31 Jul 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the donor notes parameter in all versions up to, and including, 4.5.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with GiveWP worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Additionally, they need to trick an administrator into visiting the legacy version of the site. CVE record
- CVE-2025-4571, 19 Jun 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized view and modification of data due to an insufficient capability check on the permissionsCheck functions in all versions up to, and including, 4.3.0. This makes it possible for authenticated attackers, with Contributor-level access and above, to view or delete fundraising campaigns, view donors' data, modify campaign events, etc. CVE record
- CVE-2025-2331, 22 Mar 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.22.1 via a misconfigured capability check in the 'permissionsCheck' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive data including reports detailing donors and donation amounts. CVE record
- CVE-2025-2025, 15 Mar 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the give_reports_earnings() function in all versions up to, and including, 3.22.0. This makes it possible for unauthenticated attackers to disclose sensitive information included within earnings reports. CVE record
- CVE-2025-0912, 4 Mar 2025
- The Donations Widget plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.19.4 via deserialization of untrusted input from the Donation Form through the 'card_address' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to achieve remote code execution. CVE record
- CVE-2024-12877, 11 Jan 2025
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.19.2 via deserialization of untrusted input from the donation form like 'firstName'. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to delete arbitrary files on the server that makes remote code execution possible. Please note this was only partially patched in 3.19.3, a fully sufficient patch was not released until 3.19.4. However, another CVE was assigned by another CNA for version 3.19.3 so we will leave this as affecting 3.19.2 and before. We have recommended the vendor use JSON encoding to prevent any further deserialization vulnerabilities from being present. CVE record
- CVE-2024-11921, 27 Dec 2024
- The GiveWP WordPress plugin before 3.19.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin. CVE record
- CVE-2024-9634, 16 Oct 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.16.3 via deserialization of untrusted input from the give_company_name parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to achieve remote code execution. CVE record
- CVE-2024-8353, 28 Sep 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.16.1 via deserialization of untrusted input via several parameters like 'give_title' and 'card_address'. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to delete arbitrary files and achieve remote code execution. This is essentially the same vulnerability as CVE-2024-5932, however, it was discovered the the presence of stripslashes_deep on user_info allows the is_serialized check to be bypassed. This issue was mostly patched in 3.16.1, but further hardening was added in 3.16.2. CVE record
- CVE-2024-9130, 27 Sep 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter in all versions up to, and including, 3.16.1 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 GiveWP Manager-level access and above, to append additional SQL queries into already existing queries within the Legacy View mode, that can be used to extract sensitive information from the database. CVE record
- CVE-2024-6551, 29 Aug 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.15.1. This is due to the plugin utilizing Symfony and leaving display_errors on within test files. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website. CVE record
- CVE-2024-5941, 20 Aug 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized access and deletion of data due to a missing capability check on the 'handle_request' function in all versions up to, and including, 3.14.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read attachment paths and delete attachment files. CVE record
- CVE-2024-5932, 20 Aug 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files. CVE record
- CVE-2024-5939, 20 Aug 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'setup_wizard' function in all versions up to, and including, 3.13.0. This makes it possible for unauthenticated attackers to read the setup wizard administrative pages. CVE record
- CVE-2024-5940, 20 Aug 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'handle_request' function in all versions up to, and including, 3.13.0. This makes it possible for unauthenticated attackers to edit event ticket settings if the Events beta feature is enabled. CVE record
- CVE-2024-5977, 19 Jul 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.13.0 via the 'handleRequest' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with GiveWP Worker-level access and above, to delete and update arbitrary posts. CVE record
- CVE-2024-3714, 18 May 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'give_form' shortcode when used with a legacy form in all versions up to, and including, 3.10.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1957, 13 Apr 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'give_form' shortcode in all versions up to, and including, 3.6.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1424, 9 Apr 2024
- The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in all versions up to, and including, 3.5.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-0224, 16 Jan 2024
- The GiveWP WordPress plugin before 2.24.1 does not properly escape user input before it reaches SQL queries, which could let unauthenticated attackers perform SQL Injection attacks CVE record
- CVE-2023-4246, 11 Jan 2024
- The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.33.3. This is due to missing or incorrect nonce validation on the give_sendwp_remote_install_handler function. This makes it possible for unauthenticated attackers to install and activate the SendWP plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2023-4247, 11 Jan 2024
- The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.33.3. This is due to missing or incorrect nonce validation on the give_sendwp_disconnect function. This makes it possible for unauthenticated attackers to deactivate the SendWP plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2023-4248, 11 Jan 2024
- The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.33.3. This is due to missing or incorrect nonce validation on the give_stripe_disconnect_connect_stripe_account function. This makes it possible for unauthenticated attackers to deactivate the plugin's stripe integration settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2022-4448, 13 Feb 2023
- The GiveWP WordPress plugin before 2.24.0 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks CVE record
- CVE-2022-2215, 1 Aug 2022
- The GiveWP WordPress plugin before 2.21.3 does not properly sanitise and escape the currency settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2022-2260, 1 Aug 2022
- The GiveWP WordPress plugin before 2.21.3 does not have CSRF in place when exporting data, and does not validate the exporting parameters such as dates, which could allow attackers to make a logged in admin DoS the web server via a CSRF attack as the plugin will try to retrieve data from the database many times which leads to overwhelm the target's CPU. CVE record
- CVE-2022-28700, 21 Jul 2022
- Authenticated Arbitrary File Creation via Export function vulnerability in GiveWP's GiveWP plugin <= 2.20.2 at WordPress. CVE record
- CVE-2022-31475, 21 Jul 2022
- Authenticated (custom plugin role) Arbitrary File Read via Export function vulnerability in GiveWP's GiveWP plugin <= 2.20.2 at WordPress. CVE record
- CVE-2022-2117, 18 Jul 2022
- The GiveWP plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions up to, and including, 2.20.2 via the /donor-wall REST-API endpoint which provides unauthenticated users with donor information even when the donor wall is not enabled. This functionality has been completely removed in version 2.20.2. CVE record
- CVE-2022-0252, 21 Feb 2022
- The GiveWP WordPress plugin before 2.17.3 does not escape the json parameter before outputting it back in an attribute in the Import admin dashboard, leading to a Reflected Cross-Site Scripting CVE record
- CVE-2021-25099, 21 Feb 2022
- The GiveWP WordPress plugin before 2.17.3 does not sanitise and escape the form_id parameter before outputting it back in the response of an unauthenticated request via the give_checkout_login AJAX action, leading to a Reflected Cross-Site Scripting CVE record
- CVE-2021-25100, 21 Feb 2022
- The GiveWP WordPress plugin before 2.17.3 does not escape the s parameter before outputting it back in an attribute in the Donation Forms dashboard, leading to a Reflected Cross-Site Scripting CVE record
- CVE-2021-24524, 23 Aug 2021
- The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.12.0 did not escape the Donation Level setting of its Donation Forms, allowing high privilege users to use Cross-Site Scripting payloads in them. CVE record
- CVE-2021-24315, 17 May 2021
- The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.10.4 did not sanitise or escape the Background Image field of its Stripe Checkout Setting and Logo field in its Email settings, leading to authenticated (admin+) Stored XSS issues. CVE record
- CVE-2021-24213, 12 Apr 2021
- The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.10.0 was affected by a reflected Cross-Site Scripting vulnerability inside of the administration panel, via the 's' GET parameter on the Donors page. CVE record
- CVE-2019-15317, 22 Aug 2019
- The give plugin before 2.4.7 for WordPress has XSS via a donor name. CVE record
What to do if you run GiveWP
If you run GiveWP, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GiveWP vulnerabilities
Free. We email you when a new vulnerability is published for GiveWP, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.