CVE-2026-32753 FreeScout: Stored XSS through SVG file upload with filter bypass

High 8.5 Published Updated

Authenticated attackers can upload malicious SVG files disguised as PNGs to execute JavaScript in other users' browsers, potentially hijacking accounts.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-32753?

CVE-2026-32753 is a high-severity cross-site scripting vulnerability in freescout-help-desk freescout, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. In versions 1.8.208 and below, bypasses of the attachment view logic and SVG sanitizer make it possible to upload and render an SVG that runs malicious JavaScript. An extension of .png with content type of image/svg+xml is allowed, and a fallback mechanism on invalid XML leads to unsafe sanitization. The application restricts which uploaded files are rendered inline: only files considered "safe" are displayed in the browser; others are served with Content-Disposition: attachment. This decision is based on two checks: the file extension (e.g. .png is allowed, while .svg may not be) and the declared Content-Type (e.g. image/* is allowed). By using a filename with an allowed extension (e.g. xss.png) and a Content-Type of image/svg+xml, an attacker can satisfy both checks and cause the server to treat the upload as a safe image and render it inline, even though the body is SVG and can contain scripted behavior. Any authenticated user can set up a specific URL, and whenever another user or administrator visits it, XSS can perform any action on their behalf. This issue has been fixed in version 1.8.209.

Weakness: CWE-80

Which versions are affected by CVE-2026-32753?

It affects 1 product.

Products include Freescout Freescout.

How do I fix CVE-2026-32753?

No fix has been published for CVE-2026-32753 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-32753 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32753 exists.

Sources

Also known as GHSA-cvr8-cw5c-5pfw.

Is CVE-2026-32753 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free