CVE-2024-37510
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 · uneditedMissing Authorization vulnerability in Charitable Donations & Fundraising Team Charitable allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Charitable: from n/a through 1.8.1.7.
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 · moderate confidenceMissing authorization vulnerability in the Charitable WordPress plugin allows users to access functionality that is not properly constrained by access control lists (ACLs). This broken access control issue enables authenticated users to potentially perform actions outside their intended permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Charitable plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Charitable' in the list of active pluginsAffected if Charitable plugin is not present in the plugins list
-
Determine installed version of CharitableClick on the plugin name or view the details to read the Version number displayed beneath the plugin name in the plugins listAffected if Version number cannot be retrieved from the plugin header
-
Compare version against affected rangeDocument your installed version and compare it to the version range identified in CVE-2024-37510 (if the CVE reference provides specific vulnerable versions)Affected if Installed version falls within the vulnerable version range
-
Verify authorization on sensitive functionsLog in with a low-privileged user account (subscriber/contributor) and attempt to access admin functionality or campaign management features that should require higher capabilitiesAffected if Lower-privileged user can access functionality that should be restricted to administrators or higher roles
-
Check user role capabilitiesNavigate to Users > Roles in WordPress admin, or use a role testing plugin to verify that non-administrator roles lack the manage_options or campaign management capabilitiesAffected if Users with limited roles can perform actions reserved for administrator-level capabilities
Your environment is affected if the Charitable plugin is installed and your version falls within the vulnerable range, or if low-privileged user accounts can access restricted administrative functionality
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper authorization checks and capability verification on all sensitive functionality to ensure users can only access resources and actions appropriate to their role.
Charitable 1.8.1.8 or later (latest version)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the 'Charitable' plugin in the list
- 4. If an update is available, click 'Update Now' to update to the latest version
- 5. Verify the update completed successfully
- 6. Test the charitable donation functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37510 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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