dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-37506

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing 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 confidence

Missing Authorization vulnerability in the Charitable WordPress plugin allows users to access functionality that should be constrained by Access Control Lists (ACLs). The plugin fails to properly validate user permissions before allowing access to certain features, potentially permitting unauthorized users to perform actions outside their intended permissions.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive functionality endpoints to ensure users can only access resources and actions permitted by their role-based 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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify Charitable plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and confirm the Charitable plugin is listed and active
    Affected if Charitable plugin is installed and active on the WordPress site
  2. Determine installed plugin version
    In the plugins list, locate the Charitable plugin and note the version number displayed under the plugin name, or read the version from the main plugin file header in wp-content/plugins/charitable/charitable.php
    Affected if The installed version matches or falls within the affected version range for this CVE
  3. Identify user role configuration
    Go to Users > All Users in WordPress admin and review which user roles exist on the site, noting any users assigned to roles with limited permissions (subscriber, contributor, author, editor)
    Affected if Users with limited roles exist on the site who should not have access to donation management or campaign administration features
  4. Test restricted functionality access
    Using a low-privilege user account (such as subscriber), attempt to access donation management endpoints, campaign creation interfaces, or donor data views that should be restricted to administrators only. Check browser response or API returns.
    Affected if A user with limited permissions can access features or data that should require administrator-level capabilities

The environment is affected if the Charitable plugin is installed, the version is within the affected range, and users with insufficient privileges can access restricted administrative functionality.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (capability checks and nonce verification) on all sensitive functionality endpoints to ensure users can only access resources and actions permitted by their role-based permissions.

Recommended fix Moderate confidence

Charitable version higher than 1.8.1.7 (check WordPress plugin repository for latest release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Charitable' plugin in the list
  4. Check if the current version is 1.8.1.7 or lower - if so, an update is needed
  5. Go to Plugins > Add New > Upload or check for updates via the WordPress updates page
  6. Update Charitable to the latest available version
Caveat Review plugin changelog for any breaking changes between your version and the latest release before updating

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37506 — 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-2024-37506 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