Quick answers
- Is CVE-2026-72719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72719 being exploited in the wild.
- How severe is CVE-2026-72719?
- Medium severity, with a CVSS score of 6.7, published 10 August 2026.
- Which products and versions are affected?
- Chatwoot prior to 4.9.0.
- Is there a fix for CVE-2026-72719?
- A patch was published on 2025-12-20: Fix merged in version 4.9.0 via commit 86da3f7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72719 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72719?
- 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
The vulnerability is a privilege escalation and broken access control flaw in Chatwoot's resource management controllers. The root cause is that the account_id parameter was included in Rails strong parameters for the portals, automation rules, macros, and Twilio channels controllers, allowing an authenticated administrator to modify the account_id field during resource updates. An authenticated attacker with admin privileges can submit crafted API requests with a modified account_id to transfer resources between accounts without authorization. The fix, released in version 4.9.0, removes the account_id parameter from the permitted strong parameters in the four affected controllers, preventing unauthorized account transfers.
Affected products
- Chatwoot Chatwoot prior to 4.9.0
Timeline
- 2026-08-10: disclosed
- 2025-12-20: patched: Fix merged in version 4.9.0 via commit 86da3f7