dbcve.org
Cryptocurrency WidgetsWordPress extension · Coolplugins

CVE-2023-36681

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 2.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Cool Plugins Cryptocurrency Widgets – Price Ticker & Coins List allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Cryptocurrency Widgets – Price Ticker & Coins List: from n/a through 2.6.2.

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

The Cryptocurrency Widgets – Price Ticker & Coins List WordPress plugin (versions through 2.6.2) has a missing authorization vulnerability where the plugin fails to properly enforce access control checks on certain functionality. This allows attackers to exploit incorrectly configured security levels, potentially enabling unauthenticated or unauthorized users to access sensitive operations or data that should be restricted to privileged users.

MitigationImplement proper authorization checks (capability verification and nonce validation) on all sensitive plugin functions and AJAX endpoints to ensure only authorized users can access protected functionality.

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
Affected:< 2.6.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cryptocurrency Widgets - Price Ticker & Coins List' or check the plugin header in wp-content/plugins/cryptocurrency-widgets/price-ticker.php for the Version defined
    Affected if Version is below 2.6.3 (versions 2.6.2 and earlier are affected)
  2. Identify plugin AJAX actions
    Search the plugin directory (wp-content/plugins/cryptocurrency-widgets/) for add_action('wp_ajax_') and add_action('wp_ajax_nopriv_') calls to enumerate all AJAX endpoints
    Affected if AJAX endpoints exist that lack capability checks (check for current_user_can() or nonce verification)
  3. Verify authorization on AJAX endpoints
    Inspect the PHP files containing AJAX handlers - look for current_user_can() calls and wp_verify_nonce() or check_admin_referer() before performing sensitive operations
    Affected if Sensitive functions lack proper capability verification (current_user_can('manage_options') or similar) or nonce validation
  4. Check for nopriv accessibility
    Review AJAX action registrations for 'wp_ajax_nopriv_' hooks which allow unauthenticated access
    Affected if Any sensitive plugin functions are hooked to wp_ajax_nopriv_ without proper authorization checks

Your environment is affected if the Cryptocurrency Widgets plugin version is 2.6.2 or earlier and sensitive AJAX endpoints or functions are accessible without proper capability verification or nonce validation.

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 2.6.3 or later
Fixed in 2.6.3
Interim mitigation

Implement proper authorization checks (capability verification and nonce validation) on all sensitive plugin functions and AJAX endpoints to ensure only authorized users can access protected functionality.

Recommended fix High confidence

2.6.3

  1. Backup your WordPress site before performing any updates
  2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. Find the 'Cryptocurrency Widgets – Price Ticker & Coins List' plugin
  4. Click 'Update now' if an update is available, or manually upload version 2.6.3 or later from the WordPress repository
  5. Verify the plugin version shows 2.6.3 or higher after updating
  6. Test that the plugin functionality works as expected
Caveat Minor plugin update; no breaking changes expected for typical use cases

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

Fix this in Cryptocurrency Widgets Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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