CVE-2026-118193 — WordPress
HIGHCVE-2026-118193 is a high-severity (CVSS 8.8) Improper Privilege Management vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
The 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`…
Description
The 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.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
The records we use list no fixed release for CVE-2026-118193. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-118193 in your dependencies?
Find it across your dependency tree, including transitive dependencies.