Charitable stored XSS in Stripe payment method parameter
smub Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns)
smub Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns)
| Product | Affected | Fixed in |
|---|---|---|
| smub Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns) |
| No fix yet |
The Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'stripe_payment_method' parameter in all versions up to, and including, 1.8.15.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nonce required to reach the nopriv AJAX endpoint is publicly obtainable from any rendered campaign donation form, making exploitation trivially accessible to unauthenticated visitors on sites with Stripe configured as a payment gateway.
From the CVE record · Wordfence
The Charitable WordPress plugin is vulnerable to stored cross-site scripting through the stripe_payment_method parameter. On sites with Stripe configured as a payment gateway, an unauthenticated attacker can obtain the required nonce from a rendered campaign donation form and inject scripts that execute when a user visits the affected page.
Operators of the Charitable – Donation & Fundraising Platform WordPress plugin should check installations running version 1.8.15.1 or earlier.