Givewp – Donation Plugin And Fundraising Platform
Approved changes feed: RSS · Atom
cpe:2.3:a:stellarwp:givewp_–_donation_plugin_and_fundraising_platform:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Stellarwp (85cedc32-4162-5fac-82cb-4647b1b8e38d) |
|---|---|
| Product | Givewp – Donation Plugin And Fundraising Platform (f12bff9e-7ea6-5be5-afef-be1c92233ef9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-118193 |
vulnerable | 2026-11-19 05:28:43.217177 |
GiveWP <= 4.19.1 - Authenticated (Custom+) Privilege Escalation to 'donor_default_user_role' Parameter
HIGH (8.8)
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.
Published: 2026-11-05T04:48:07.930Z
Updated: 2026-11-05T20:40:02.169Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-14987 |
vulnerable | 2026-07-29 00:26:17.695866 |
GiveWP <= 4.16.3 - Authenticated (Give Worker+) Stored Cross-Site Scripting via 'twitter_message' Sequoia Template Setting
MEDIUM (6.4)
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'twitter_message' Sequoia Template Setting in all versions up to, and including, 4.16.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with give worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected script executes specifically when a donor clicks the Share on Twitter button on the Sequoia donation confirmation view, as that is when the unescaped twitter_message value is evaluated inside the JavaScript template literal.
Published: 2026-07-16T02:30:56.586Z
Updated: 2026-07-16T12:45:22.534Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-13704 |
vulnerable | 2026-07-29 00:23:33.232028 |
GiveWP <= 4.16.1 - Authenticated (Give Worker+) Stored Cross-Site Scripting via Sequioa Form
MEDIUM (6.4)
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sequoia[introduction][image]' parameter in all versions up to, and including, 4.16.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Give Worker-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published: 2026-07-02T05:35:14.362Z
Updated: 2026-07-02T12:35:05.389Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-13246 |
vulnerable | 2026-07-29 00:23:32.931933 |
GiveWP <= 4.16.0 - Authenticated (Author+) Stored Cross-Site Scripting via 'block_id' Shortcode Attribute
MEDIUM (6.4)
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'block_id' (and other) shortcode attributes of the 'givewp_campaign_comments' shortcode in versions up to, and including, 4.16.0. This is due to insufficient input sanitization and output escaping on user supplied attributes in CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render(), where the blockId value is interpolated directly into a single-quoted HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published: 2026-07-01T03:43:33.891Z
Updated: 2026-07-01T10:42:12.021Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-11981 |
vulnerable | 2026-07-29 00:23:31.847052 |
GiveWP <= 4.15.3 - Cross-Site Request Forgery
MEDIUM (4.3)
The GiveWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.15.3 This is due to missing nonce validation on the give_set_notification_status_handler() function. This makes it possible for unauthenticated attackers to disable donation email notifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2026-07-01T04:32:26.862Z
Updated: 2026-07-01T10:42:11.276Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-8620 |
vulnerable | 2026-06-08 07:45:20.814233 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-7221 |
vulnerable | 2026-06-08 07:43:18.167040 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-7205 |
vulnerable | 2026-06-08 07:43:18.144701 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-4571 |
vulnerable | 2026-06-08 07:29:16.461635 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-2331 |
vulnerable | 2026-06-08 07:16:56.806559 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-2025 |
vulnerable | 2026-06-08 07:14:57.785036 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-13206 |
vulnerable | 2026-06-08 07:04:31.789050 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-11228 |
vulnerable | 2026-06-08 07:02:28.290118 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-11227 |
vulnerable | 2026-06-08 07:02:28.289688 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-0912 |
vulnerable | 2026-06-08 07:02:25.893167 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9634 |
vulnerable | 2026-06-08 07:00:28.356191 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9130 |
vulnerable | 2026-06-08 07:00:26.706210 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-8353 |
vulnerable | 2026-06-08 07:00:24.321133 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-6551 |
vulnerable | 2026-06-08 06:58:19.827961 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5977 |
vulnerable | 2026-06-08 06:56:18.158499 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5941 |
vulnerable | 2026-06-08 06:56:18.053481 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5940 |
vulnerable | 2026-06-08 06:56:18.051918 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5939 |
vulnerable | 2026-06-08 06:56:18.049947 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5932 |
vulnerable | 2026-06-08 06:56:18.040999 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-3714 |
vulnerable | 2026-06-08 06:43:51.263790 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1957 |
vulnerable | 2026-06-08 06:27:15.128283 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1424 |
vulnerable | 2026-06-08 06:25:40.041848 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-12877 |
vulnerable | 2026-06-08 06:25:36.263115 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4248 |
vulnerable | 2026-06-08 06:16:11.896350 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4247 |
vulnerable | 2026-06-08 06:16:11.895617 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4246 |
vulnerable | 2026-06-08 06:16:11.893770 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-2117 |
vulnerable | 2026-06-08 05:42:50.304688 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.