CVE-2026-5205 | chatwoot up to 4.11.2 Webhook API lib/webhooks/trigger.rb Webhooks::Trigger url server-side request forgery
VulDBArchived Mar 31, 2026✓ Full text saved
A vulnerability was found in chatwoot up to 4.11.2 . It has been declared as critical . Affected by this vulnerability is the function Webhooks::Trigger in the library lib/webhooks/trigger.rb of the component Webhook API . Such manipulation of the argument url leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2026-5205 . The attack can be launched remotely. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respo
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354333 · CVE-2026-5205 · GCVE-100-354333
CHATWOOT UP TO 4.11.2 WEBHOOK API LIB/WEBHOOKS/TRIGGER.RB WEBHOOKS::TRIGGER URL SERVER-SIDE REQUEST FORGERY
HISTORYDIFFRELATEJSONXMLCTI
Summaryinfo
A vulnerability was found in chatwoot up to 4.11.2. It has been rated as critical. Affected by this issue is the function Webhooks::Trigger in the library lib/webhooks/trigger.rb of the component Webhook API. Performing a manipulation of the argument url results in server-side request forgery. This vulnerability was named CVE-2026-5205. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure but did not respond in any way.
Detailsinfo
A vulnerability, which was classified as critical, was found in chatwoot up to 4.11.2. This affects the function Webhooks::Trigger in the library lib/webhooks/trigger.rb of the component Webhook API. The manipulation of the argument url with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability.
This vulnerability is uniquely identified as CVE-2026-5205. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.
It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Type
Chat Software
Name
chatwoot
Version
4.11.0
4.11.1
4.11.2
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Server-side request forgery
CWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/31/2026 Advisory disclosed
03/31/2026 +0 days VulDB entry created
03/31/2026 +0 days VulDB entry last update
Sourcesinfo
Status: Not defined
CVE: CVE-2026-5205 (🔒)
GCVE (CVE): GCVE-0-2026-5205
GCVE (VulDB): GCVE-100-354333
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 03/31/2026 10:53
Changes: 03/31/2026 10:53 (56)
Complete: 🔍
Submitter: Ghufran Khan
Cache ID: 99:982:101
Submitinfo
Accepted
Submit #780305: Chatwoot 4.11.2 Server-Side Request Forgery (by Ghufran Khan)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸