dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6093

MEDIUM · 6.0 CVSS v4.0 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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
Corteza contains a SQL injection vulnerability in its Microsoft SQL Server (MSSQL) backend when filtering Compose records by the meta field.This issue affects corteza: 2024.9.8.

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

Corteza contains a SQL injection vulnerability in its Microsoft SQL Server (MSSQL) backend when filtering Compose records by the meta field. An attacker could exploit this by injecting malicious SQL queries through the meta field filter, potentially allowing unauthorized data access or manipulation.

MitigationUpgrade to a patched version of Corteza beyond 2024.9.8. Until a fix is available, restrict access to Compose record filtering functionality and validate input sanitization for the meta field.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed Corteza version
    Check the version file or running instance metadata (e.g., look for version information in the Corteza admin panel, docker labels, or Helm chart values)
    Affected if The installed version is prior to 2024.9.8 (the patched release)
  2. Confirm Microsoft SQL Server is the backend database
    Inspect the Corteza configuration file (typically docker-compose.yml, config.yaml, or environment variables) for the DB_TYPE or DATABASE_URL setting pointing to MSSQL
    Affected if The backend database is Microsoft SQL Server (MSSQL)
  3. Verify the Compose module is in use
    Check if the Compose (low-code) module is enabled in the Corteza instance by reviewing the modules configuration or checking for compose-related API endpoints
    Affected if The Compose module is enabled and accessible to users
  4. Determine if meta field filtering is accessible
    Test or inspect whether the Compose record filtering functionality exposes the meta field as a filterable attribute in the UI or API (review API responses for filterable fields)
    Affected if The meta field is exposed as a filterable option in Compose record filtering

A user is affected if they are running Corteza versions before 2024.9.8 with MSSQL as the backend and the Compose module with meta field filtering enabled and accessible.

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

Upgrade to a patched version of Corteza beyond 2024.9.8. Until a fix is available, restrict access to Compose record filtering functionality and validate input sanitization for the meta field.

Recommended fix Moderate confidence

Latest stable Corteza release (contact vendor or check GitHub releases for the patched version)

  1. 1. Back up your current Corteza installation and database before making any changes.
  2. 2. Identify your current Corteza version by checking the application or deployment configuration.
  3. 3. Obtain the latest stable release of Corteza from the official repository (github.com/cortezaproject/corteza).
  4. 4. Upgrade your Corteza installation to the most recent stable release that addresses the MSSQL SQL injection vulnerability in the Compose records meta field filtering.
  5. 5. After upgrade, verify that the SQL injection vulnerability is resolved by testing Compose record filtering with the meta field on your MSSQL backend.
  6. 6. Monitor application logs for any SQL errors or unexpected behavior following the upgrade.
Caveat Review release notes for any breaking changes between 2024.9.8 and the target upgrade version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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