dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-53776

HIGH · 7.1 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in raphaelheide Donate Me donate-me allows Stored XSS.This issue affects Donate Me: from n/a through <= 1.2.5.

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

A CSRF vulnerability in the Donate Me WordPress plugin (versions <= 1.2.5) enables attackers to craft malicious requests that, when triggered by an authenticated administrator, inject and store malicious JavaScript payloads (Stored XSS) into the plugin's data storage. When other users view the affected content, the stored script executes in their browsers, potentially stealing session cookies or performing actions on behalf of victims.

MitigationImplement anti-CSRF tokens and origin validation for all state-changing operations, and apply strict input validation with context-aware output encoding to prevent stored XSS injection.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 checks

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

  1. Verify Donate Me plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Donate Me' in the list of active plugins.
    Affected if The Donate Me plugin appears in the installed plugins list, regardless of activation status
  2. Check installed plugin version
    In the Plugins list, locate the Donate Me plugin and note the version number displayed beneath the plugin name. Compare this version against the affected range: versions 1.2.5 and earlier.
    Affected if The installed version is 1.2.5 or any earlier version number
  3. Inspect plugin settings for unexpected content
    Navigate to the Donate Me plugin settings page (usually under Settings or a dedicated Donate Me menu item). Review all text fields, donation forms, or message configuration areas for any suspicious JavaScript tags, script elements, or encoded payloads that were not intentionally added.
    Affected if Any unfamiliar or malicious-looking script content is present in plugin configuration fields
  4. Review stored data for XSS payloads
    Access the WordPress database via phpMyAdmin or wp-cli and query the Donate Me plugin tables for stored entries (such as donation records, messages, or custom fields). Look for HTML script tags, javascript: URIs, or event handler attributes in the data fields.
    Affected if Database records contain script tags, event handlers, or other XSS payloads that were not purposefully configured by an administrator

A user is affected if the Donate Me plugin is installed with version 1.2.5 or earlier, or if malicious scripts are found stored in the plugin's data or settings.

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 anti-CSRF tokens and origin validation for all state-changing operations, and apply strict input validation with context-aware output encoding to prevent stored XSS injection.

Recommended fix Moderate confidence

Latest available version of Donate Me (check repository for 1.2.6 or higher)

  1. Check the WordPress plugin repository or Patchstack for the latest version of the Donate Me plugin
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate the Donate Me plugin
  4. If a newer version is available, click Update Now to upgrade to the latest secure version
  5. After updating, verify the plugin is functioning correctly on your site
  6. Consider reviewing the plugin's changelog to confirm the security fix is included

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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