VulnerabilityPublished 19 Mar 2026

CVE-2026-32753: freescout · Basic XSS

Affects freescoutSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 1.8.209 soon.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8.209

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade freescout and freescout-help-desk/freescout to 1.8.209.

Affected software

Product	Affected	Fixed in
freescout-help-deskfreescout	Affected <1.8.209	Fixed in 1.8.209
GitHubfreescout-help-desk/freescout`pkg:github/freescout-help-desk/freescout`Other threats	Affected <1.8.209	Fixed in 1.8.209

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade FreeScout to version 1.8.209 or later, where this vulnerability is fixed. Beyond patching, implement strict server-side validation of uploaded files, ensuring that file extensions and MIME types are consistent and that SVG files are either disallowed or sanitized using robust, well-maintained libraries. Disable inline rendering of user-uploaded SVG files unless absolutely necessary and consider converting SVGs to safer formats before display. Employ Content Security Policy (CSP) headers to restrict script execution and reduce XSS impact. Monitor logs for suspicious file uploads and access patterns. Limit upload permissions to trusted users and enforce multi-factor authentication to reduce the risk of compromised accounts being used to exploit this vulnerability. Regularly audit and test file upload functionalities for similar weaknesses.

Description

CVE-2026-32753 is a high-severity cross-site scripting (XSS) vulnerability in FreeScout versions prior to 1.8.209. It arises from improper sanitization of SVG files masquerading as PNG images, allowing authenticated users to upload malicious SVG content that executes JavaScript when rendered inline. The vulnerability exploits the application's file extension and content-type checks, which incorrectly permit SVG payloads with a . png extension and image/svg+xml content type to bypass security controls. When another user or administrator views the malicious attachment, the embedded script executes with their privileges, enabling actions on their behalf without their consent. This flaw affects the confidentiality and integrity of user sessions and data. The issue has been fixed in version 1.8.

Impact

This vulnerability poses a significant risk to organizations using FreeScout versions prior to 1.8.209. Successful exploitation allows attackers with valid user credentials to execute arbitrary JavaScript in the context of other users, including administrators. This can lead to session hijacking, unauthorized access to sensitive information, manipulation of help desk tickets, and potential lateral movement within the organization’s infrastructure. The integrity and confidentiality of user data and communications are at risk, as attackers can perform actions on behalf of victims without their knowledge. Since FreeScout is often used in customer support and internal communication, exploitation could disrupt business operations and damage trust. The vulnerability’s ease of exploitation—requiring only authenticated access and no user interaction beyond visiting a crafted URL—amplifies its threat. Although no known exploits are reported in the wild yet, the high CVSS score (8.5) reflects the critical nature of this flaw.

Summary

CVE-2026-32753 is a cross-site scripting (XSS) vulnerability classified under CWE-80, affecting FreeScout, a PHP Laravel-based help desk and shared inbox application. In versions 1.8.208 and earlier, the application’s logic for handling uploaded attachments and sanitizing SVG files is flawed. FreeScout restricts inline rendering of uploaded files based on file extension and declared Content-Type headers, allowing only files deemed 'safe' to be displayed inline in browsers. However, an attacker can upload an SVG file containing malicious JavaScript by naming it with an allowed extension such as .png and setting the Content-Type to image/svg+xml. This bypasses the extension and content-type checks, causing the server to treat the file as a safe image and render it inline. The SVG content can include script elements that execute when the file is viewed, leading to XSS. The fallback mechanism on invalid XML further weakens the SVG sanitizer, increasing the attack surface. Exploitation requires an authenticated user to upload the malicious file and create a URL that, when visited by other users or administrators, triggers the script execution. This can lead to session hijacking, unauthorized actions, or data theft. The vulnerability was addressed in FreeScout version 1.8.209 by improving file validation and sanitization processes.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:33 UTC

WeaknessesCWE-80

Technical details

References

Community reviews

Related threats