Cryptocurrency WidgetsWordPress extension · Coolplugins
CVE-2024-43304
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 · uneditedImproper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Cool Plugins Cryptocurrency Widgets – Price Ticker & Coins List allows Reflected XSS.This issue affects Cryptocurrency Widgets – Price Ticker & Coins List: from n/a through 2.8.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 · high confidenceReflected XSS vulnerability in the Cryptocurrency Widgets – Price Ticker & Coins List WordPress plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web page responses.
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
Cryptocurrency WidgetsWordPress extension
< 2.8.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, locate 'Cryptocurrency Widgets - Price Ticker & Coins List', and read the version number displayed beneath the plugin name. Alternatively, open the main plugin file (usually /wp-content/plugins/cryptocurrency-widgets-by-coolplugins/index.php or similar) and look for the 'Version:' header in the plugin comments.Affected if The installed version is lower than 2.8.1 (e.g., 2.8.0, 2.7.x, etc.)
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that the Cryptocurrency Widgets plugin shows as 'Active'. A deactivated plugin with a vulnerable version is not exploitable.Affected if The plugin is activated and the version is below 2.8.1
-
Identify exposed ticker endpointsReview the website's publicly accessible pages that render cryptocurrency price tickers or coin lists. These are typically shortcode-based (e.g., [cryptocurrency_price_ticker_widget] or similar) embedded in pages/posts or widgetized areas. Note which URL parameters are accepted on pages displaying the widget.Affected if Public-facing pages render the cryptocurrency ticker widget and accept URL parameters without sanitization; the vulnerable code reflects user input in the page response.
-
Inspect server access logs for XSS probe attemptsSearch web server access logs (Apache, Nginx, or WAF logs) for patterns like '<script>', 'javascript:', or other XSS payloads in URLs containing the plugin's shortcode or widget parameters. Use grep or similar: grep -i 'script' /var/log/apache2/access.log | grep -i 'cryptocurrency'Affected if Log entries show suspicious URL parameters containing XSS payloads being passed to pages that render the widget
You are affected if the Cryptocurrency Widgets plugin is active and the installed version is below 2.8.1, with the widget's shortcode or functionality exposed on publicly accessible pages.
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 · scoped2.8.1
Update to version 2.8.1 or later which contains the patch; alternatively, apply input validation/sanitization and output encoding to all user-supplied parameters before reflecting them in HTML responses.
2.8.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Cryptocurrency Widgets – Price Ticker & Coins List' by Cool Plugins
- Click 'Update now' if an update to version 2.8.1 is available, or manually upload version 2.8.1 of the plugin
- After updating, verify the plugin version shows 2.8.1 under Plugins > Installed Plugins
- Clear any site caches if caching plugins are in use
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cryptocurrency Widgets
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-43304 — 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-43304 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