dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39596

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-17
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
Unauthenticated SQL Injection in Blocksy Companion Pro < 2.1.29 versions.

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 confidence

Unauthenticated SQL injection vulnerability in Blocksy Companion Pro plugin for WordPress allows remote attackers to inject malicious SQL queries via unsanitized input, potentially leading to data exfiltration or complete database compromise.

MitigationUpdate Blocksy Companion Pro to version 2.1.29 or later to patch the SQL injection vulnerability. If immediate update is not possible, deploy a WAF rule to block SQL injection attack patterns.

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 Blocksy Companion Pro is installed
    Navigate to WordPress admin > Plugins and locate 'Blocksy Companion Pro' in the installed plugins list, or inspect the file /wp-content/plugins/blocksy-companion-pro/blocksy-companion.php
    Affected if The plugin is installed and active in WordPress
  2. Determine installed plugin version
    In WordPress admin > Plugins, click 'View Details' on Blocksy Companion Pro to display the version number, or open /wp-content/plugins/blocksy-companion-pro/blocksy-companion.php and search for 'Version:' in the plugin header comment
    Affected if The displayed version is lower than 2.1.29 (e.g., 2.1.28 or earlier)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the Blocksy Companion Pro shows as 'Active' (not deactivated or deleted)
    Affected if The plugin is currently active on the WordPress site
  4. Check for suspicious database activity
    Review WordPress database logs or error logs for unusual SQL queries containing UNION, SELECT, or DROP statements from unknown IP addresses targeting the blocksy-companion endpoints
    Affected if Unexpected SQL commands appear in logs that were not initiated by legitimate admin actions

Your environment is affected if Blocksy Companion Pro is installed, active, and running on a version before 2.1.29.

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

Update Blocksy Companion Pro to version 2.1.29 or later to patch the SQL injection vulnerability. If immediate update is not possible, deploy a WAF rule to block SQL injection attack patterns.

Recommended fix High confidence

2.1.29 or later

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Locate 'Blocksy Companion Pro' in the plugin list
  4. Update the plugin to version 2.1.29 or later if an update is available, or manually upload the new version
  5. Verify the update was successful by checking the installed plugin version
Caveat Minor plugin updates typically do not introduce breaking changes; test in staging if concerned

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

Have this fixed 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 help mitigating

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-2026-39596 — 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-2026-39596 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