CVE-2022-22798
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 · uneditedSysaid – Pro Plus Edition, SysAid Help Desk Broken Access Control v20.4.74 b10, v22.1.20 b62, v22.1.30 b49 - An attacker needs to log in as a guest after that the system redirects him to the service portal or EndUserPortal.JSP, then he needs to change the path in the URL to /ConcurrentLogin%2ejsp after that he will receive an error message with a login button, by clicking on it, he will connect to the system dashboard. The attacker can receive sensitive data like server details, usernames, workstations, etc. He can also perform actions such as uploading files, deleting calls from the system.
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 confidenceSysaid Help Desk software contains a broken access control vulnerability where authenticated guest users can escalate privileges by manipulating the URL to access /ConcurrentLogin%2ejsp, which grants them full dashboard access. This allows unauthorized viewing of sensitive system information (server details, usernames, workstations) and administrative actions including file uploads and call deletion.
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< 21.1.50< 22.1.64CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Sysaid installation and versionLocate the Sysaid installation directory and check version files, or query the application directly via its web interface or API for the version numberAffected if The installed version is lower than 21.1.50 or lower than 22.1.64 (for versions using the 22.x branch)
-
Verify guest user account configurationCheck if any user account in Sysaid is configured with guest-level or limited permissions that should restrict access to administrative featuresAffected if Guest or limited user accounts exist in the system that should not have administrative access
-
Test ConcurrentLogin endpoint accessibilityAttempt to access the /ConcurrentLogin%2ejsp endpoint (URL-encoded as /ConcurrentLogin.jsp) using an authenticated guest user session to verify if it grants elevated accessAffected if A guest user can access /ConcurrentLogin.jsp and gains full dashboard functionality beyond their authorized permissions
-
Inspect dashboard access controlsLog in with a non-administrative guest account and attempt to view sensitive system information (server details, usernames, workstations) or perform administrative actions (file uploads, call deletion)Affected if Guest users can view sensitive system information or execute administrative actions they should not be authorized to perform
Your environment is affected if you are running Sysaid versions below 21.1.50 or below 22.1.64 and guest users can access the ConcurrentLogin endpoint or gain administrative dashboard functionality.
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 · scoped21.1.5022.1.64
Implement proper server-side authorization checks on all endpoints to ensure guest users cannot access administrative or privileged functionality. Validate user session permissions before allowing access to dashboard features and restrict the ConcurrentLogin functionality to prevent privilege escalation.
Sysaid 21.1.50 or 22.1.64 (upgrade to the fixed release corresponding to your current branch)
- Identify your current Sysaid version and determine which release branch (21.x or 22.x) you are running
- Create a complete backup of the Sysaid database and configuration files before proceeding with the upgrade
- Download Sysaid version 21.1.50 (if on 21.x branch) or version 22.1.64 (if on 22.x branch) from the official Sysaid vendor portal
- Follow the official Sysaid upgrade documentation to apply the patch to your environment
- After upgrading, verify that the Broken Access Control vulnerability is fixed by testing the URL manipulation vector (attempting to access /ConcurrentLogin%2ejsp as a guest should no longer succeed)
- Confirm that guest users can only access their designated portal areas and cannot reach administrative functions or sensitive data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22798 — 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-2022-22798 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