CVE-2025-5275 MEDIUM

CVE-2025-5275: Charitable <= 1.8.6.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via Plugin's Privacy Settings

Vendor Smub
Product Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More
Weakness CWE-79 · XSS
Published June 26, 2025
Last update April 8, 2026

CVSS base score

4.4/10
Attack vector Network
Attack complexity High
Privileges required High
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the privacy settings fields in all versions up to, and including, 1.8.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. This issue was partially fixed in version 1.8.6.1 and fully fixed in version 1.8.6.2.

Explanation of Vulnerability in Simple Terms

02Summary

The Charitable donation plugin for WordPress contains a cross-site scripting (XSS) vulnerability in versions up to 1.8.6.1. An attacker with high-level site privileges can inject malicious scripts that affect other users or site functionality. The vulnerability requires specific conditions to exploit and has limited impact on confidentiality and integrity.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers or affect site functionality.

Potential impact on your site

04Site Impact

A compromised admin or editor account could inject scripts affecting other users or site behavior without additional user clicks.

Conditions required to exploit

05Prerequisites

Attacker must have high-level WordPress privileges (e.g., administrator or editor role). No user interaction required.

Key dates

06Disclosure timeline

June 26, 2025 CVE published
April 8, 2026 Record updated