dbcve.org
Cryptocurrency Widgets PackWordPress extension · Blocksera

CVE-2022-44588

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-15
Fix available
A fix is available. Upgrade to after 1.8.1 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
Unauth. SQL Injection vulnerability in Cryptocurrency Widgets Pack Plugin <=1.8.1 on WordPress.

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

An unauthenticated SQL injection vulnerability exists in the Cryptocurrency Widgets Pack WordPress plugin version 1.8.1 and earlier, allowing remote attackers to inject malicious SQL queries via unsanitized input parameters in the plugin's frontend widgets.

MitigationUpdate the Cryptocurrency Widgets Pack plugin to version 1.8.2 or later to remediate the vulnerability. If an update is unavailable, consider removing the plugin until a patch is released.

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 Widgets PackWordPress extension
Affected:<= 1.8.1

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 installed plugin version
    Navigate to WordPress Admin > Plugins > Cryptocurrency Widgets Pack and note the version number displayed, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version displayed is 1.8.1 or lower
  2. Confirm plugin is active
    In WordPress Admin > Plugins, verify the Cryptocurrency Widgets Pack plugin shows as 'Active'
    Affected if The plugin is active and running
  3. Check for exposed frontend widgets
    Visit your website's frontend pages where cryptocurrency widgets may be embedded (commonly sidebars, footers, or dedicated pages) and inspect if any price display or crypto-related widgets are rendering publicly
    Affected if Frontend widgets are publicly accessible without authentication
  4. Inspect widget parameters for injection points
    Use browser developer tools to examine the HTML source of any active cryptocurrency widgets and identify input parameters (such as coin IDs, currency selectors, or display options) passed via URL query strings or form inputs
    Affected if Widget parameters are visible in the page source and can be modified by unauthenticated users

Your environment is affected if the Cryptocurrency Widgets Pack plugin version is 1.8.1 or earlier AND the plugin is active with frontend widgets exposed to unauthenticated users.

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 a release after 1.8.1
Interim mitigation

Update the Cryptocurrency Widgets Pack plugin to version 1.8.2 or later to remediate the vulnerability. If an update is unavailable, consider removing the plugin until a patch is released.

Recommended fix Moderate confidence

Latest version of Cryptocurrency Widgets Pack (verify 1.8.2 or higher on wordpress.org)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Cryptocurrency Widgets Pack
  4. Check if an update is available and update to the latest version
  5. Alternatively, navigate to Dashboard > Updates and update all plugins
  6. Verify the update was successful by checking the plugin version after updating

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

Fix this in Cryptocurrency Widgets Pack Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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