Chatwoot: SQL Injection in Conversation/Contact Filter API via Custom Attribute Values
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| chatwoot | chatwoot | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Chatwoot | Chatwoot |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.227% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Chatwoot
Chatwoot chatwoot |
|
| Vendors & Products |
Chatwoot
Chatwoot chatwoot |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Chatwoot: SQL Injection in Conversation/Contact Filter API via Custom Attribute Values | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|