dbcve.org
CharitableWordPress extension · Wpcharitable

CVE-2021-24531

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-23
Fix available
A fix is available. Upgrade to 1.6.51 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Charitable – Donation Plugin WordPress plugin before 1.6.51 is affected by an authenticated stored cross-site scripting vulnerability which was found in the add donation feature.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Charitable WordPress donation plugin before version 1.6.51 contains an authenticated stored cross-site scripting (XSS) vulnerability in the add donation feature. An authenticated attacker can inject malicious JavaScript into donation form fields, which is then stored in the database and executed when administrators view the donation data.

MitigationUpdate Charitable – Donation Plugin to version 1.6.51 or later to obtain the patched version. Review donation entries for any existing malicious scripts that may have been injected prior to patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CharitableWordPress extension
Affected:< 1.6.51

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Charitable plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/charitable/ directory exists on the server
    Affected if The Charitable plugin directory exists in the WordPress installation
  2. Check the installed version number
    In WordPress admin, go to Plugins > Installed Plugins > Charitable and view the version number, or read the version from charitable/readme.txt or charitable/changelog.php
    Affected if The installed version is earlier than 1.6.51 (versions like 1.6.50, 1.6.49, etc.)
  3. Determine if donation form submissions are accessible
    Verify that the site allows authenticated users (donors, subscribers, or custom roles) to submit donations through the plugin's donation form
    Affected if Authenticated users can access and submit donation forms on the site
  4. Inspect stored donation data for malicious content
    In WordPress admin, navigate to Charitable > Donations and review each donation entry, examining all donor input fields (name, email, address fields, and custom fields) for unescaped HTML, script tags, or JavaScript code
    Affected if Any donation entry contains unescaped HTML tags, script elements, or suspicious JavaScript code in donor input fields

A user is affected if the Charitable plugin is installed with a version earlier than 1.6.51 AND authenticated users can submit donations, or if malicious scripts already exist in stored donation data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.51 or later
Fixed in 1.6.51
Interim mitigation

Update Charitable – Donation Plugin to version 1.6.51 or later to obtain the patched version. Review donation entries for any existing malicious scripts that may have been injected prior to patching.

Recommended fix High confidence

1.6.51

  1. 1. Create a full backup of your WordPress database and files
  2. 2. Log in to your WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Locate the Charitable plugin in the list
  5. 5. If an update is available, click 'Update now' to upgrade to version 1.6.51
  6. 6. Alternatively, download version 1.6.51 from the official WordPress plugin repository and upload it manually
  7. 7. After updating, verify the installed version shows 1.6.51
  8. 8. Test the donation functionality to confirm the plugin operates correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Charitable Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-24531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-24531 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data