CVE-2026-23758
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGFI HelpDesk before 4.99.9 contains a stored cross-site scripting vulnerability in the ticket subject field that allows authenticated staff members to inject malicious JavaScript by manipulating the editsubject POST parameter. Attackers can inject XSS payloads through inadequate sanitization in Controller_Ticket.EditSubmit() that bypass the incomplete SanitizeForXSS() method to execute arbitrary JavaScript when other staff members or administrators view the affected ticket.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGFI HelpDesk before version 4.99.9 contains a stored cross-site scripting vulnerability in the ticket subject field. Authenticated staff members can inject malicious JavaScript through the editsubject POST parameter in Controller_Ticket.EditSubmit() by bypassing an incomplete SanitizeForXSS() method. The injected payload executes when other staff or administrators view the affected ticket.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.99.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GFI HelpDesk installed versionLocate the version information in the GFI HelpDesk installation - typically found in the admin panel under System Information, About, or in a version file within the installation directory. Compare the installed version number to the affected range: versions prior to 4.99.9 are vulnerable.Affected if Installed version is GFI HelpDesk < 4.99.9
-
Verify staff authentication access existsConfirm that staff or administrator accounts exist and can log into GFI HelpDesk. The vulnerability requires an authenticated staff member to submit the malicious editsubject parameter.Affected if Staff or administrator accounts are active and can access the ticket management system
-
Confirm ticket edit functionality is enabledNavigate to the ticket management interface and verify that staff members can edit ticket subjects. The vulnerable endpoint is Controller_Ticket.EditSubmit() which processes the editsubject POST parameter.Affected if Ticket editing functionality is available to authenticated staff members
-
Inspect ticket subject display mechanismExamine how ticket subjects are rendered in the staff/admin ticket view pages. The stored XSS executes when viewing tickets with malicious subjects.Affected if Ticket subjects are displayed without proper context-aware output encoding
A user is affected if they are running GFI HelpDesk version below 4.99.9 with active staff accounts that have access to edit ticket subjects.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.99.9
Implement robust input validation and context-aware output encoding in Controller_Ticket.EditSubmit() to properly sanitize the editsubject parameter, ensuring the SanitizeForXSS() method comprehensively handles all XSS vectors before storing and displaying ticket subjects.
4.99.9
- Backup the current GFI Helpdesk installation and database before proceeding with the upgrade
- Upgrade GFI Helpdesk to version 4.99.9 or later where the stored XSS vulnerability is fixed
- After upgrading, verify the Controller_Ticket.EditSubmit() method now properly sanitizes the editsubject POST parameter
- Test that XSS payloads in the ticket subject field are properly neutralized and do not execute when viewed by other staff or administrators
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23758 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data