What happened
GiveWP is a WordPress plugin that websites use to accept online donations and run fundraising campaigns. It is developed by Liquid Web / StellarWP. Security company Patchstack has disclosed a login verification flaw affecting all versions up to and including 4.16.9.
The flaw was reported by researcher Abdelrhman Allam on August 10, 2026. Patchstack published it in its database on September 24, 2026, and it appeared in the US National Vulnerability Database (NVD) on September 30, 2026 as CVE-2026-97196. Version 4.17.0 contains the fix.
Patchstack notes that another CVE Numbering Authority also published the same flaw as CVE-2026-82675. It is the same issue, and a single update resolves both entries.
Is it being exploited? No exploitation is known so far. The CISA KEV catalog does not list it, and ENISA’s European vulnerability database EUVD (entry EUVD-2026-89655) records no exploitation. Patchstack does, however, warn that the flaw is highly dangerous and expected to be exploited.
Why it is dangerous
This is a broken authentication flaw. Patchstack describes it as letting attackers bypass the login system or log in as other users without their password. The NVD entry classifies it as CWE-1289: the application mishandles inputs that look different but are treated by the system as equivalent.
Picture a receptionist who lets people in based on a name list. If they treat two slightly different spellings of a name as the same person, a stranger can walk in as an employee. In a similar way, the plugin misjudges who is actually logging in.
According to Patchstack, the attacker needs no account or password, the attack runs over the internet directly against the website, and the victim does not have to do anything. Patchstack does not say which accounts can be reached this way. If it were an administrator account, however, WordPress would normally allow changing content and settings, installing plugins (and thereby running arbitrary code on the server), and reading donor data.
The CVSS score of 9.1 out of 10 (critical) was assigned by Patchstack using CVSS version 3.1. CVSS is a standard severity scale. The high number reflects that the attack works over the network, is simple, requires no login or user interaction, and seriously threatens data confidentiality and integrity. Website availability is not directly affected according to the rating.
The CISA KEV catalog lists vulnerabilities whose exploitation the US agency CISA has confirmed. This flaw is not on it yet. EPSS estimates the likelihood of exploitation in the next 30 days: as of November 19, 2026 it stood at 0.44%, higher than roughly 39% of known vulnerabilities.
A low EPSS does not mean you are safe. Patchstack warns that flaws like this are used in mass exploitation campaigns that automatically hit thousands of websites at once, regardless of their traffic or popularity.
Who is affected
It affects every WordPress site with the GiveWP plugin (found in the plugins folder as give) at version 4.16.9 or older. Patchstack lists the vulnerable versions as “<= 4.16.9”, meaning everything up to and including 4.16.9.
GiveWP is typically used by nonprofits, foundations, associations, churches, schools and companies that collect donations or run fundraisers on their website. These sites usually run on shared web hosting or on a dedicated WordPress server. Because the attack requires no login, any publicly reachable site running a vulnerable version is at risk.
Sites running GiveWP 4.17.0 or later, and sites that do not use GiveWP, are not affected. Do not forget old test copies and staging sites that may still contain the plugin.
How to check if you are affected
The easiest way is the WordPress dashboard: go to “Plugins” > “Installed Plugins”, find GiveWP and read the version number in the line below its description.
If you have server access and WP-CLI, run this command in the site directory. It changes nothing and only prints the version:
wp plugin get give --field=version
To list all plugins with their versions and status:
wp plugin list --fields=name,status,version
Without WP-CLI, you can read the header of the plugin’s main file:
grep -i "Version:" wp-content/plugins/give/give.php
If the version is 4.16.9 or lower, the site is vulnerable. If you manage several sites, check each one separately.
How to fix it
The fixed version is GiveWP 4.17.0. Patchstack advises updating immediately to 4.17.0 or later. If you cannot do it yourself, ask your hosting provider or web developer for help.
- Back up the site, both files and database, ideally with your hosting provider’s tools.
- In the dashboard, open “Plugins” and click “Update now” next to GiveWP, or use the WP-CLI command below.
- Confirm that version 4.17.0 or higher is shown and test a donation form.
- Start with public and business-critical sites, then update or remove test and old installations.
- If your environment allows it, enable automatic updates for GiveWP.
wp plugin update give
If you cannot update right away: Patchstack says it has issued a mitigation rule for customers of its service that blocks attacks until the update is applied. As a general stopgap, you can deactivate GiveWP until you update, or ask your host to block attacks with a web application firewall (WAF). Keep in mind that deactivating the plugin temporarily stops donations.
The flaw is not in the CISA KEV catalog, so CISA has not set a mandatory remediation deadline for it. Do not postpone the update anyway.
What if you may already be compromised
Neither Patchstack nor NVD has published specific indicators of compromise. Because the flaw lets attackers log in as other users, look for signs of unauthorized access to the dashboard, especially since September 24, 2026, when the flaw was disclosed.
- Unknown user accounts, particularly with the administrator role, or changed email addresses on existing accounts.
- Plugins and themes you did not install, and unfamiliar PHP files in
wp-content. - Changes to GiveWP settings, especially payment gateways and notification emails.
- Web server logs (on shared hosting, look in your hosting control panel): dashboard access from unknown IP addresses at unusual times.
List administrators with their email and registration date:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
PHP files changed in the last 60 days. The output also includes files changed by regular updates, so focus on unfamiliar names and files outside the plugin and theme folders:
find wp-content -name "*.php" -mtime -60
If you find anything, change all administrator passwords and log out all sessions. Since GiveWP handles donors’ personal data, also review your GDPR obligations. If you suspect a breach or are unsure, bring in a security professional or your hosting provider’s technical support.