dbcve.org
Help DeskApplication · Sysaid

CVE-2022-40324

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-11
Fix available
A fix is available. Upgrade to 22.1.65 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
SysAid Help Desk before 22.1.65 allows XSS via the Linked SRs field, aka FR# 67258.

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

This is a Cross-Site Scripting (XSS) vulnerability in SysAid Help Desk software affecting versions prior to 22.1.65. The vulnerability exists in the 'Linked SRs' field (service request linking feature), allowing an attacker to inject malicious JavaScript code that executes in the browsers of other users viewing the affected field.

MitigationUpgrade SysAid Help Desk to version 22.1.65 or later which contains the fix for this XSS vulnerability. As a compensating control, implement output encoding on the Linked SRs field and enforce Content Security Policy headers.

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
Help DeskApplication
Affected:< 22.1.65

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 SysAid Help Desk version
    Access the SysAid administration console and navigate to the About or System Information section, typically found under Settings > System > About. Alternatively, check the login page footer or the installer file properties if accessible.
    Affected if The installed version number is lower than 22.1.65 (for example, 22.1.64, 22.1.50, 21.x, etc.)
  2. Confirm the Linked SRs feature exists
    Log in as a standard user or administrator and create a new service request (SR) or open an existing one. Look for a field labeled 'Linked SRs' or 'Link to Service Request' within the service request form.
    Affected if The Linked SRs field is present and accessible in the service request interface
  3. Inspect for injected script content
    Review existing service requests in the system, specifically examining any entries in the Linked SRs field. Check for unusual characters, HTML tags, or JavaScript code that may have been inserted into linked request IDs.
    Affected if The Linked SRs field contains unexpected HTML tags (such as <script>, <img>, <iframe>) or JavaScript event handlers (onload, onerror, onclick) in what should be plain request identifiers

A user is affected if they are running SysAid Help Desk versions prior to 22.1.65 and the Linked SRs field contains or could contain unsanitized input with script content.

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 22.1.65 or later
Fixed in 22.1.65
Interim mitigation

Upgrade SysAid Help Desk to version 22.1.65 or later which contains the fix for this XSS vulnerability. As a compensating control, implement output encoding on the Linked SRs field and enforce Content Security Policy headers.

Recommended fix Moderate confidence

22.1.65

  1. Back up your current SysAid Help Desk installation and database before proceeding with any upgrade
  2. Download SysAid Help Desk version 22.1.65 from the official SysAid download portal or vendor distribution channels
  3. Follow the standard SysAid upgrade procedure for your installation type (on-premise or managed)
  4. After upgrading, verify that the Linked SRs field no longer accepts unsanitized input by testing with benign script tags
  5. Confirm the XSS vulnerability is resolved by reviewing release notes or patch documentation for version 22.1.65

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

Fix this in Help Desk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40324 — 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-2022-40324 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