CVE-2026-23757
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.10 contains a stored cross-site scripting vulnerability in the Reports module where the title parameter is passed directly to SWIFT_Report::Create() without HTML sanitization. Attackers can inject arbitrary JavaScript into the report title field when creating or editing a report, and the payload executes when staff members view and click the affected report link in the Manage Reports interface.
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.10 contains a stored cross-site scripting vulnerability in the Reports module where the report title parameter is passed directly to SWIFT_Report::Create() without HTML sanitization, allowing attackers to inject arbitrary JavaScript that executes when staff view the affected report in the Manage Reports interface.
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.10CVSS 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.
-
Check installed GFI HelpDesk versionLocate the version file or check the software metadata. Common paths include the admin interface (usually under Help > About or System > Settings), a version.php file in the installation directory, or the database settings table.Affected if The installed version is below 4.99.10 (e.g., 4.5, 4.0, 3.x)
-
Verify Reports module is enabledLog into the GFI HelpDesk admin panel and navigate to the module or settings section to confirm the Reports module is active. Alternatively, check the database for records in the reports-related tables.Affected if The Reports module is enabled and accessible to staff users
-
Inspect existing report titles for XSS payloadsQuery the database (typically the swreports or similar table) for report titles containing HTML tags such as <script>, <img>, <iframe>, onerror, onload, or javascript: URIs. If direct database access is unavailable, view each report through the Manage Reports interface and inspect the page source for unsanitized output.Affected if Any report title contains unescaped HTML or JavaScript code that executes when viewed
-
Check user permissions for report creationVerify that low-privilege or non-admin users have the ability to create reports. Test creating a new report with a simple HTML test payload (e.g., <b>test</b>) and confirm whether it is rendered as bold or as plain text.Affected if Users without admin privileges can create reports and the input is rendered without sanitization
You are affected if GFI HelpDesk version is below 4.99.10 and the Reports module is accessible, allowing stored XSS via the report title parameter to execute in the Manage Reports interface.
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.10
Upgrade to GFI HelpDesk version 4.99.10 or later which implements proper HTML sanitization for the report title parameter before storage and rendering.
4.99.10
- Upgrade GFI HelpDesk to version 4.99.10 or later to resolve the stored XSS vulnerability in the Reports module.
- After upgrading, verify the fix by attempting to create a report with a test HTML/JavaScript payload in the title field to confirm sanitization is applied.
- Review other input fields in the Reports module for similar vulnerabilities.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23757 — 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-23757 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