Improper Restriction of Excessive Authentication Attempts in chatwoot/chatwoot
Impact varies for each individual vulnerability in the application. For generation of accounts, it may be possible, depending on the amount of system resources available, to create a DoS event in the server. These accounts still need to be activated; however, it is possible to identify the output Status Code to separate accounts that are generated and waiting for email verification. \n\nFor the sign in directories, it is possible to brute force login attempts to either login portal, which could lead to account compromise.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-3741
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 02:19 UTC · Revision 1
Source evidence
Improper Restriction of Excessive Authentication Attempts in chatwoot/chatwoot
core-osv · Original sourcePublished 28 Oct 2022, 00:00 UTC
Impact varies for each individual vulnerability in the application. For generation of accounts, it may be possible, depending on the amount of system resources available, to create a DoS event in the server. These accounts still need to be activated; however, it is possible to identify the output Status Code to separate accounts that are generated and waiting for email verification. \n\nFor the sign in directories, it is possible to brute force login attempts to either login portal, which could lead to account compromise.
osv:CVE-2022-3741
Complete source record
{
"id": "bbd3781ed50d3529c8b00642a6aafa35e62ca0648fca3b86115c3722ff31e4c4",
"url": "https://osv.dev/vulnerability/CVE-2022-3741",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Improper Restriction of Excessive Authentication Attempts in chatwoot/chatwoot",
"summary": "Impact varies for each individual vulnerability in the application. For generation of accounts, it may be possible, depending on the amount of system resources available, to create a DoS event in the server. These accounts still need to be activated; however, it is possible to identify the output Status Code to separate accounts that are generated and waiting for email verification. \\n\\nFor the sign in directories, it is possible to brute force login attempts to either login portal, which could lead to account compromise.",
"evidence": "osv:CVE-2022-3741",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2022-3741",
"aliases": [
"CVE-2022-3741"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/chatwoot/chatwoot",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "ce9c8645df2899dd508836d4dbc3448db8e13d33"
},
{
"fixed": "9525d4f0346a2fdac13a0253f9180d20104a72d3"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:chatwoot:chatwoot:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "2.10.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "9525d4f0346a2fdac13a0253f9180d20104a72d3"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v2.9.1",
"v2.9.0",
"v2.8.1",
"v2.8.0",
"v2.7.0",
"v2.6.0",
"v2.5.0",
"v2.4.1",
"v2.4.0",
"v2.3.2",
"v2.3.1",
"v2.3.0",
"v2.2.1",
"v2.2.0",
"v2.1.1",
"v2.1.0",
"v2.0.2",
"v2.0.1",
"v2.0.0",
"v1.22.1",
"v1.22.0",
"v1.21.1",
"v1.21.0",
"v1.20.0",
"v1.19.0",
"v1.18.1",
"v1.18.0",
"v1.17.1",
"v1.17.0",
"v1.16.2",
"v1.16.1",
"v1.15.1",
"v1.15.0",
"v1.14.3",
"v1.14.2",
"v1.14.1",
"v1.14.0",
"v1.13.1",
"v1.13.0",
"v1.12.2",
"v1.12.1",
"v1.12.0",
"v1.11.1",
"v1.11.0",
"v1.10.0",
"v1.9.0",
"v1.8.0",
"v1.7.2",
"v1.7.1",
"v1.7.0",
"v1.6.3",
"v1.6.2",
"v1.6.1",
"v1.6.0",
"v1.5.3",
"v1.5.2",
"v1.5.1",
"v1.5.0",
"v1.4.2",
"1.4.2",
"v1.4.1",
"v1.4.0",
"v1.3.0",
"v1.2.4",
"1.2.4",
"v1.2.3",
"v1.2.2",
"v1.2.1",
"v1.2.0",
"v1.1.3",
"v1.1.2",
"v1.1.1",
"v1.1.0",
"v1.0.3",
"v1.0.2",
"v1.0.1",
"v1.0.0",
"v0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-3741.json"
}
}
],
"modified": "2026-10-28T02:30:25.588876593Z",
"provider": "osv",
"references": [
"https://huntr.dev/bounties/46f6e07e-f438-4540-938a-510047f987d0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/3xxx/CVE-2022-3741.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-3741",
"https://github.com/chatwoot/chatwoot/commit/9525d4f0346a2fdac13a0253f9180d20104a72d3"
],
"provider_metadata": {
"cwe_ids": [
"CWE-307"
],
"cna_assigner": "@huntrdev",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/3xxx/CVE-2022-3741.json"
}
},
"related_cves": [
{
"value": "CVE-2022-3741",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 491851,
"published_at": "2022-10-28T00:00:00+00:00"
}