CVE-2026-44706: Chatwoot SQL injection in conversation and contact filter APIs

CVE-2026-44706 · Severity: high · CVSS 8.5 · Published 2026-05-26

Chatwoot is a customer engagement platform used by businesses to manage communications with their clients. A security flaw in the platform's filtering system allows an authorized user to bypass security boundaries and access sensitive information belonging to other accounts. This could lead to the theft of customer data, private conversation logs, user email addresses, and encrypted password hashes.

Technologies: Chatwoot. Vendors: Chatwoot.

Quick answers

Is CVE-2026-44706 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44706 being exploited in the wild.
How severe is CVE-2026-44706?
High severity, with a CVSS score of 8.5, published 26 May 2026.
Which products and versions are affected?
Chatwoot 2.2.0 to 4.11.1.
Is there a fix for CVE-2026-44706?
A patch was published on 2026-05-26: Fix released in version 4.11.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44706 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44706?
Check whether you run Chatwoot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A SQL injection vulnerability exists in Chatwoot's conversation and contact filter APIs due to improper parameterization of user-supplied values. When filtering by custom attributes of type 'date' or 'number' using 'is_greater_than' or 'is_less_than' operators, input is interpolated directly into SQL queries. Additionally, the 'attribute_key' field in custom attribute definitions was found to be vulnerable to injection. An authenticated attacker with low privileges can utilize time-based blind SQL injection to exfiltrate data across tenant boundaries, including bcrypt password hashes and API tokens. The vulnerability is fixed in version 4.11.2 by enforcing strict attribute key formats and using 'sanitize_sql_array' for bind parameters.

Affected products

  • Chatwoot Chatwoot 2.2.0 to 4.11.1

Timeline

  • 2026-05-05: advisory: GitHub advisory published by maintainers
  • 2026-05-26: disclosed: CVE published to NVD
  • 2026-05-26: patched: Fix released in version 4.11.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.