dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-40783

CRITICAL · 9.9 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 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
Contributor Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.37 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 · moderate confidence

A Remote Code Execution vulnerability in Blocksy Companion Pro WordPress plugin allows users with contributor-level permissions to execute arbitrary code on the server. This is particularly severe because contributor roles typically only have limited content editing capabilities without server execution rights.

MitigationUpdate Blocksy Companion Pro to a version newer than 2.1.37 immediately. Until patched, consider restricting or disabling contributor-level user accounts if not business-critical.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Verify Blocksy Companion Pro is installed
    Navigate to WordPress Admin > Plugins and look for 'Blocksy Companion Pro' in the installed plugins list, or check the file system at /wp-content/plugins/blocksy-companion-pro/ for the main plugin file
    Affected if Plugin is not found in the plugins directory
  2. Determine the installed plugin version
    In WordPress Admin, go to Plugins > Installed Plugins > Blocksy Companion Pro and read the version number displayed below the plugin name, or inspect the main plugin file header for 'Version:' value
    Affected if Version is 2.1.37 or earlier (any version prior to the patched release)
  3. Confirm the plugin is active
    In WordPress Admin > Plugins, verify that Blocksy Companion Pro shows as 'Active' rather than 'Inactive' or 'Deactivated'
    Affected if Plugin is active and version is 2.1.37 or earlier
  4. Identify contributor-level user accounts
    In WordPress Admin > Users, filter or scroll through the user list and identify any accounts with the 'Contributor' role assigned
    Affected if At least one user with Contributor role exists on the site

The environment is affected if Blocksy Companion Pro version 2.1.37 or earlier is active on the WordPress site and at least one user with Contributor role exists, as the vulnerability allows those limited users to execute arbitrary code.

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 Blocksy Companion Pro to a version newer than 2.1.37 immediately. Until patched, consider restricting or disabling contributor-level user accounts if not business-critical.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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