dbcve.org
HelpdeskApplication · Gfi

CVE-2026-23756

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-20
Fix available
A fix is available. Upgrade to 4.99.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
GFI HelpDesk before 4.99.9 contains a stored cross-site scripting vulnerability in the Troubleshooter module where the subject POST parameter is not sanitized in Controller_Step.InsertSubmit() and EditSubmit() before being rendered by View_Step.RenderViewSteps(). An authenticated staff member can inject arbitrary JavaScript into the step subject field, and the payload executes when any user navigates to Troubleshooter > View Troubleshooter and clicks the affected step link.

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 confidence

GFI HelpDesk before version 4.99.9 has a stored XSS vulnerability in the Troubleshooter module. The subject POST parameter in Controller_Step.InsertSubmit() and EditSubmit() methods is not sanitized before being rendered by View_Step.RenderViewSteps(). An authenticated staff member can inject arbitrary JavaScript that executes when other users view and click the affected step link.

MitigationUpgrade GFI HelpDesk to version 4.99.9 or later. Until upgrade, restrict access to the Troubleshooter module to trusted staff only.

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
HelpdeskApplication
Affected:< 4.99.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GFI HelpDesk installation and version
    Locate the GFI HelpDesk installation and determine the installed version number. This is typically found in the software's about page, a version file, or the database configuration.
    Affected if The installed version is lower than 4.99.9 (for example, 4.5, 4.7, 4.98)
  2. Verify the Troubleshooter module is accessible
    Confirm that the Troubleshooter module is enabled and accessible to authenticated staff members. This may be visible in the application navigation or configurable in the module settings.
    Affected if The Troubleshooter module is enabled and available to staff accounts
  3. Check for existing staff accounts
    Verify if there are any authenticated staff member accounts in the system that have access to the Troubleshooter module functionality.
    Affected if There are staff accounts with access to create or edit troubleshooting steps
  4. Inspect step data in the database
    Examine the database tables storing Troubleshooter step information, specifically looking at records that may contain the 'subject' field populated by the Controller_Step methods. Look for unexpected HTML or script tags in these fields.
    Affected if Database records in the Troubleshooter step tables contain unsanitized script tags or JavaScript event handlers in subject fields

A user is affected if they run GFI HelpDesk version lower than 4.99.9, the Troubleshooter module is enabled, and untrusted staff can access it to inject malicious script content into step subject fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.99.9 or later
Fixed in 4.99.9
Interim mitigation

Upgrade GFI HelpDesk to version 4.99.9 or later. Until upgrade, restrict access to the Troubleshooter module to trusted staff only.

Recommended fix High confidence

4.99.9

  1. 1. Back up the current GFI Helpdesk installation and database before proceeding with any upgrade
  2. 2. Download GFI Helpdesk version 4.99.9 from the official GFI vendor website
  3. 3. Apply the upgrade to the production environment following standard GFI upgrade procedures
  4. 4. Verify the upgrade was successful by logging into the Helpdesk as an administrator
  5. 5. Navigate to Troubleshooter > View Troubleshooter and confirm the application functions normally
  6. 6. Test that previously created step subjects render correctly without script execution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Helpdesk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23756 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23756 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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