dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-44706

HIGH · 8.5 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Chatwoot is a customer engagement suite. From 2.2.0 to before 4.11.2, a SQL injection vulnerability exists in the conversation and contact filter APIs. When filtering by a custom attribute of type date or number using the is_greater_than or is_less_than operators, user-supplied values in the values field of the filter payload are interpolated directly into the SQL query without parameterization. Any authenticated user with access to an account can exploit this to execute arbitrary SQL via time-based blind injection. This affects /api/v1/accounts/{account_id}/conversations/filter, /api/v1/accounts/{account_id}/contacts/filter, and /api/v1/accounts/{account_id}/custom_attribute_definitions. This vulnerability is fixed in 4.11.2.

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

SQL injection vulnerability in Chatwoot's conversation and contact filter APIs allows authenticated users to inject arbitrary SQL by supplying crafted values in filter payloads when using is_greater_than or is_less_than operators on date/number custom attributes. User-supplied values are directly interpolated into SQL queries without parameterization, enabling time-based blind injection attacks.

MitigationUpgrade Chatwoot to version 4.11.2 or later. If immediate upgrade is not feasible, restrict access to the affected filter endpoints (/api/v1/accounts/{account_id}/conversations/filter, /api/v1/accounts/{account_id}/contacts/filter, /api/v1/accounts/{account_id}/custom_attribute_definitions) pending patch application.

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
Low
Availability
None

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

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 Chatwoot installation and version
    Locate the Chatwoot installation and check the version file or API endpoint that returns version info (typically in the application root or via /api/v1/health endpoint)
    Affected if The installed version is earlier than 4.11.2
  2. Verify conversation filter API accessibility
    Confirm the conversation filter API endpoint exists and is accessible (typically /api/v1/conversations/filters or similar path)
    Affected if The API endpoint is exposed to authenticated users in the environment
  3. Verify contact filter API accessibility
    Confirm the contact filter API endpoint exists and is accessible (typically /api/v1/contacts/filters or similar path)
    Affected if The API endpoint is exposed to authenticated users in the environment
  4. Check for custom attributes of date or number type
    Inspect the Chatwoot database or admin panel for custom attribute definitions where attribute_type is 'date' or 'number'
    Affected if Custom attributes with date or number types exist in the system

A user is affected if their Chatwoot installation is version earlier than 4.11.2 AND the conversation or contact filter APIs are accessible to authenticated users AND custom attributes of date or number type exist in the system.

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 Chatwoot to version 4.11.2 or later. If immediate upgrade is not feasible, restrict access to the affected filter endpoints (/api/v1/accounts/{account_id}/conversations/filter, /api/v1/accounts/{account_id}/contacts/filter, /api/v1/accounts/{account_id}/custom_attribute_definitions) pending patch application.

Recommended fix High confidence

Upgrade from versions 2.2.0 - 4.11.1 to version 4.11.2 or later

  1. Identify the currently installed Chatwoot version using the dashboard or deployment configuration
  2. Review the Chatwoot release notes for version 4.11.2 to understand changes and any prerequisites
  3. Ensure a backup of the database and application data exists before upgrading
  4. Upgrade Chatwoot to version 4.11.2 or later by following the official upgrade guide at docs.chatwoot.com
  5. After upgrade, verify the application is functioning correctly and test the affected filter APIs to confirm the vulnerability is resolved
  6. Review application logs for any anomalies indicating exploitation attempts
Caveat Review release notes for version 4.11.2 - minor version upgrades in Chatwoot typically include bug fixes but may introduce minor UI/UX changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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