CVE-2026-118193
Last modified
CVE-2026-118193 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.40% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-118193?
How severe is CVE-2026-118193?
How do I fix CVE-2026-118193?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-118186The PublishPress Revisions: Duplicate Posts, Submit, Approve…4.9
- CVE-2026-118187The PublishPress Revisions: Duplicate Posts, Submit, Approve…2.7
- CVE-2026-118188The PublishPress Revisions: Duplicate Posts, Submit, Approve…4.3
- CVE-2026-118189The Posts Table with Search & Sort plugin for WordPress is v…6.4
- CVE-2026-11819Module: plugins/modules/keyring_info.py CVSS 3.1: 5.5 MEDI…5.5
- CVE-2026-118192The JoomSport – for Sports: Team & League, Football, Hockey …6.5
- CVE-2026-118194The Page and Post Restriction plugin for WordPress is vulner…6.5
- CVE-2026-1182GitLab has remediated an issue in GitLab CE/EE affecting all…4.3
- CVE-2026-11820A flaw was found in the community.general Ansible collection…6.5
- CVE-2026-118205The Essential Addons for Elementor – Popular Elementor Templ…7.4
- CVE-2026-11821The Eventin – Event Calendar, Event Registration, Tickets & …5.4
- CVE-2026-11822SQLite before 3.53.2 contains an out-of-bounds read vulnerab…5.5
Are you affected by CVE-2026-118193?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
