Skip to main content
Public proof of conceptFix available

CVE-2022-3741

A public proof of concept exists; no exploitation attested.

  • Published2022-10-28
  • Fixed in2.10.0
  • WeaknessCWE-307

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2022-10-2813:15CVE publishedNVD

Versions per branch

NVD
Chatwoot
BranchAffectedFixed in
2.10< 2.10.02.10.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As @huntrdev, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • chatwoot/chatwoot
    Affected
    • < v2.10.0fixed in v2.10.0custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-10-28

Fix

  1. Update Chatwoot to 2.10.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2025-05-09
  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 3.09.4known since 2026-10-23
  • CNAweakness (CWE)CWE-307known since 2026-10-23
  • NVDweakness (CWE)CWE-307read 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-11-18
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2022-10-28
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-wjg3-46v4-3f44

Frequently asked questions

What is CVE-2022-3741?

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.

Is CVE-2022-3741 actively exploited?

A proof-of-concept exploit exists for CVE-2022-3741, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2022-3741?

CVE-2022-3741 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record