Safeguard
Vulnerability Analysis•

CVE-2021-3742: High SSRF in Chatwoot via SVG Avatar Upload

CVE-2021-3742 is a high SSRF in Chatwoot before 2.5.0, reachable through an SVG avatar upload. Upgrade to Chatwoot 2.5.0 or later and limit server egress.

Safeguard Security Team
3 min read

CVE-2021-3742 is a high severity (CVSS 8.8) server side request forgery in Chatwoot, affecting versions before 2.5.0. An attacker can upload an SVG file with a malicious payload as an avatar, and opening it in a new tab can trigger the SSRF. Upgrade to Chatwoot 2.5.0 or later.

What's affected

  • Chatwoot before 2.5.0, per the record.
  • Fixed: 2.5.0, with a fix commit 6fdd4a2 referenced by the record. I could not retrieve the huntr report, so details beyond the record are unconfirmed.

The record scores it 8.8 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.

How to check if you're exposed

Check the version in your deployment, such as the image tag or the version shown in the application's settings. Anything older than 2.5.0 needs upgrading.

What to do now

  1. Find Chatwoot deployments.
  2. Read the version.
  3. Upgrade to 2.5.0 or later.
  4. Limit outbound network access from the app server to what it needs.
  5. Review uploaded avatars for SVG files.

After you patch, record the new version for Chatwoot in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.

Why it matters

The record maps the flaw to CWE-918, server side request forgery. SVG is an XML format that can reference other resources, so accepting it from users without careful handling lets the server be pointed at addresses the attacker chooses.

SSRF matters most where the server can reach internal services or cloud metadata. Egress controls and avoiding SVG for avatars are good general defenses.

To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Why is SVG risky?

SVG is XML and can reference other resources. If a server processes it, it may make requests on the attacker's behalf.

How do I find every place Chatwoot is used?

Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.