Skip to main content
VulnerabilityPublished Updated

CVE-2026-23756: GFI Software HelpDesk · Cross-site Scripting

Affects GFI Software HelpDeskSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 4.99.9 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.99.9
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade GFI Software HelpDesk to 4.99.9.

Affected software

ProductAffectedFixed in
GFI SoftwareHelpDeskAffected
  • <4.99.9
Fixed in
  • 4.99.9

AI-suggested

If you cannot patch yet, organizations should restrict staff permissions to trusted users only and consider monitoring or limiting access to the Troubleshooter module to reduce risk. Applying input validation or output encoding on the subject parameter in custom deployments may mitigate the issue.

Description

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.

References

Community reviews

Loading reviews…