dbcve.org
Codebard\'s Patron Button And Widgets For PatreonWordPress extension · Codebard

CVE-2024-33928

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to after 2.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodeBard CodeBard's Patron Button and Widgets for Patreon allows Reflected XSS.This issue affects CodeBard's Patron Button and Widgets for Patreon: from n/a through 2.2.0.

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 reflected Cross-site Scripting (XSS) vulnerability exists in CodeBard's Patron Button and Widgets for Patreon plugin (versions up to 2.2.0). The vulnerability stems from improper neutralization of user-supplied input during web page generation, allowing attackers to inject malicious scripts that execute in the context of a victim's browser.

MitigationUpdate the CodeBard Patron Button and Widgets for Patreon plugin to a version beyond 2.2.0 when available. If no patch exists, implement proper input sanitization and output encoding using WordPress escaping functions (esc_html, esc_attr, esc_js) on all user-controlled parameters before reflecting them in HTML.

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
Codebard\'s Patron Button And Widgets For PatreonWordPress extension
Affected:<= 2.2.0

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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the Codebard Patron Button and Widgets for Patreon plugin
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'patron-button-and-widgets-for-patreon' or similar Codebard Patreon-related plugin folder
    Affected if The plugin folder exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named 'patron-button-and-widgets-for-patreon.php' or similar) and look for the 'Version' header in the plugin comment block at the top of the file
    Affected if The reported version is 2.2.0 or lower (e.g., 2.2.0, 2.1.9, 2.1.0, 1.x.x)
  3. Verify the plugin is active
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and check if the Codebard Patreon plugin is currently activated
    Affected if The plugin shows as 'Active' in the WordPress plugins list
  4. Inspect for user-controlled parameters in requests
    If you have access to server logs or can capture a test request, examine any URL parameters passed to pages loading the plugin widgets (e.g., ?patron_id=, ?campaign=, or similar query parameters)
    Affected if The plugin reflects URL parameters back into the page output without proper escaping

Your environment is affected if the Codebard Patron Button and Widgets for Patreon plugin version 2.2.0 or lower is installed and active on your WordPress site, and user-supplied input from URL parameters is reflected in the page without sanitization.

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.

From vendor data
Upgrade available Upgrade to a release after 2.2.0
Interim mitigation

Update the CodeBard Patron Button and Widgets for Patreon plugin to a version beyond 2.2.0 when available. If no patch exists, implement proper input sanitization and output encoding using WordPress escaping functions (esc_html, esc_attr, esc_js) on all user-controlled parameters before reflecting them in HTML.

Fix this in Codebard\'s Patron Button And Widgets For Patreon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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