Skip to main content
← Vulnerabilities

GiveWP <= 4.19.1 - Authenticated (Custom+) Privilege Escalation to 'donor_default_user_role' Parameter

8.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
0.40% · 34th percentile
18/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

The GiveWP donation and fundraising plugin for WordPress, up to and including version 4.19.1, has a privilege escalation flaw in its donor default user role setting. An attacker who can log in with the GiveWP Manager role or higher can remotely set new donor accounts to receive elevated WordPress roles, including Administrator through the settings import path, so the attacker can gain higher access on the site.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original 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.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • stellarwp GiveWP – Donation Plugin and Fundraising Platform

    through 4.19.1

Evidence 6

  1. Link
  2. Link
  3. Link
  4. Link
  5. Link
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-118193

Is CVE-2026-118193 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-118193?

GiveWP – Donation Plugin and Fundraising Platform: through 4.19.1.Source: cve.now feed data