dbcve.org
Recurring Paypal DonationsWordPress extension · Wp Ecommerce

CVE-2024-35676

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 1.8 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in wpecommerce Recurring PayPal Donations allows Stored XSS.This issue affects Recurring PayPal Donations: from n/a through 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 · high confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the Recurring PayPal Donations WordPress plugin. The plugin fails to properly sanitize user-supplied input before reflecting it in web pages, allowing attackers to inject malicious JavaScript code that executes in the browsers of other users who view affected pages.

MitigationThe development team should implement proper input validation and output encoding using WordPress escape functions (such as esc_html(), esc_attr(), or wp_kses()) at all points where user input is displayed. Additionally, implement nonce verification for admin actions and consider adding Content Security Policy headers.

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
Recurring Paypal DonationsWordPress extension
Affected:< 1.8

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. Verify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wp Ecommerce Recurring PayPal Donations' or 'Recurring PayPal Donations'. Check the version number displayed below the plugin name. Alternatively, inspect the main plugin file (usually recurring-paypal-donations.php or similar) and look for a version comment or constant near the top.
    Affected if The installed version is lower than 1.8 (e.g., 1.7, 1.6, etc.) or if no version number is displayed (indicating an old, unupdated copy).
  2. Identify user input points
    Examine the plugin for donation forms, admin settings pages, or any features that accept user-supplied data such as donor names, email addresses, donation amounts, or custom messages. Check both frontend donation forms and WordPress admin settings pages created by the plugin.
    Affected if The plugin accepts and stores user input through any field without visible sanitization indicators (such as esc_html, esc_attr, or similar WordPress escaping functions in the code).
  3. Check for stored data in database
    If the plugin has been in use, review the WordPress database tables (typically wp_postmeta or a custom table created by the plugin) for any stored donation records or submitted form data. Use phpMyAdmin or WP-CLI to query for recent entries.
    Affected if There are stored records containing unsanitized HTML or script tags in the database that could be rendered when viewing donation lists or acknowledgment pages.

You are affected if the Recurring PayPal Donations plugin version is below 1.8 and the plugin processes or displays any user-supplied input without proper sanitization and escaping.

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.8 or later
Fixed in 1.8
Interim mitigation

The development team should implement proper input validation and output encoding using WordPress escape functions (such as esc_html(), esc_attr(), or wp_kses()) at all points where user input is displayed. Additionally, implement nonce verification for admin actions and consider adding Content Security Policy headers.

Recommended fix High confidence

Recurring PayPal Donations version 1.8

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find the 'Recurring PayPal Donations' plugin in the list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.8
  5. 5. Alternatively, you can upload the version 1.8 plugin files manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin shows version 1.8 in the plugins list
  7. 7. Test the plugin functionality to ensure the PayPal donation forms work correctly
  8. 8. Clear any site caches if you use caching plugins

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

Fix this in Recurring Paypal Donations Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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