django-helpdesk up to 2.3.2 Attachment Serving cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in django-helpdesk up to 2.3.2. This affects an unknown function of the component Attachment Serving. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2026-73531. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in django-helpdesk up to 2.3.2. It has been classified as problematic. This affects an unknown functionality of the component Attachment Serving. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

django-helpdesk before 2.3.3 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject arbitrary JavaScript by submitting HTML-formatted email messages or uploading .html/.htm file attachments through public ticket submission channels. Attackers can exploit the lack of sanitization and Content-Disposition headers at the attachment-serving layer to execute malicious scripts in the browser session of authenticated staff members who open the attachment while triaging tickets.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-73531 since 08/12/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

Upgrading to version 2.3.3 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• django-helpdesk

Version

• 2.3.0
• 2.3.1
• 2.3.2

Website

• Product: https://github.com/django-helpdesk/django-helpdesk/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion