dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-26535

CRITICAL · 9.3 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in CodeSolz Bitcoin / AltCoin Payment Gateway for WooCommerce woo-altcoin-payment-gateway allows Blind SQL Injection.This issue affects Bitcoin / AltCoin Payment Gateway for WooCommerce: from n/a through <= 1.7.6.

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

SQL injection vulnerability in the CodeSolz Bitcoin/AltCoin Payment Gateway for WooCommerce plugin allows attackers to inject malicious SQL commands through unsanitized user input. As a blind SQL injection, attackers infer database information from application response behaviors rather than direct output.

MitigationUpdate the plugin to a patched version once released, or implement proper input validation and parameterized queries at all database interaction points. Consider deploying a WAF as an interim protective measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 if the CodeSolz Bitcoin/AltCoin Payment Gateway plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'CodeSolz Bitcoin/AltCoin Payment Gateway' or check the wp-content/plugins directory for a folder containing 'codesolz' or 'btc' in the name
    Affected if The plugin is found installed and active in WordPress
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin name to view details and version number, or open the main plugin PHP file (usually in wp-content/plugins/coinpayments-wordpress or similar) and look for the 'Version' header in the plugin comment block
    Affected if The version number cannot be determined or is below any patched version that may have been released after CVE publication
  3. Confirm WooCommerce payment gateway is enabled
    Navigate to WooCommerce > Settings > Payments in WordPress admin and check if the CodeSolz Bitcoin/AltCoin Payment Gateway is listed and enabled
    Affected if The payment gateway is enabled and accepting payments, meaning user input can reach the vulnerable code path
  4. Review server access logs for suspicious SQL-like patterns
    Examine web server access logs (Apache/nginx) for requests to the plugin's payment processing endpoint containing common SQL injection payloads such as UNION, SELECT, SLEEP, BENCHMARK, or WAITFOR, particularly in parameters related to user IDs, transaction IDs, or payment addresses
    Affected if Unexpected SQL-related payloads are found in logs targeting the plugin endpoint
  5. Check for unexpected database behavior or anomalies
    Monitor application responses for unusual delays (indicative of blind SQLi time-based payloads) or examine database query logs if available for the WooCommerce orders or related tables for suspicious WHERE clause modifications
    Affected if Time delays in responses correlate with specific input patterns, or database shows unexpected queries against order/user tables originating from the plugin

The environment is affected if the CodeSolz Bitcoin/AltCoin Payment Gateway plugin is installed, enabled, and handling payment requests without being updated to a patched version released after this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version once released, or implement proper input validation and parameterized queries at all database interaction points. Consider deploying a WAF as an interim protective measure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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