CVE-2026-118193 · Package
NO FIX YET · SEE WHAT TO DO
The GiveWP donation plugin for WordPress up to and including 4.19.1 lets a user with the GiveWP Manager role set the role given to new donors, and the settings import path skips the check that blocks Administrator. An attacker can therefore make every new donor account an Administrator on the site.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the GiveWP plugin at version 4.19.1 or earlier are exposed. The attacker needs an account with the GiveWP Manager role or higher, which holds the manage_give_settings capability. Sites without GiveWP, or where only trusted staff hold that role, face much less risk.
Not affected if no-givewp-manager-users, plugin-above-4.19.1, plugin-not-installed
Who cares givewp, self-hosted, wordpress
wp plugin get give --field=versiondonor_default_user_role value in the GiveWP settings and confirm it is not a privileged role4.19.1; the sources do not name the fixed versionThe GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.19.1 via the donor_default_user_role parameter. This is due to the sanitize_option_donor_default_user_role() function applying only a narrow literal check against the string 'administrator' rather than enforcing the plugin's own give_get_donor_safe_user_roles() allowlist on save, and due to the give_core_settings_import_callback() AJAX handler writing imported JSON directly into the give_settings option via update_option() without invoking the sanitize filter at all. This makes it possible for authenticated attackers with the GiveWP Manager role (holding the manage_give_settings capability) and above to configure donor registration to assign privileged WordPress roles — up to and including Administrator via the import path — to every new donor account created through the platform. Via the settings save path, the Administrator role is blocked but any other elevated role (Editor, Author, etc.) is accepted; via the Tools › Import JSON path, the sanitize filter is bypassed entirely, allowing the Administrator role itself to be stored and subsequently applied to all newly registered donor accounts.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.