dbcve.org
SysaidApplication

CVE-2022-22796

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-12
Fix available
A fix is available. Upgrade to 21.1.30 / 21.4.45 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 – Sysaid System Takeover - An attacker can bypass the authentication process by accessing to: /wmiwizard.jsp, Then to: /ConcurrentLogin.jsp, then click on the login button, and it will redirect you to /home.jsp without any authentication.

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 · moderate confidence

This is an authentication bypass vulnerability in SysAid where unauthenticated attackers can access /wmiwizard.jsp and /ConcurrentLogin.jsp to bypass the login mechanism and reach /home.jsp without valid credentials, effectively gaining unauthorized access to the application's authenticated areas.

MitigationRestrict access to /wmiwizard.jsp and /ConcurrentLogin.jsp by enforcing proper authentication checks on these endpoints, and apply any vendor-provided security patches for SysAid.

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
SysaidApplication
Affected:< 21.1.30< 21.4.45

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify the installed SysAid version
    Locate the SysAid installation directory and check the version file or WAR file name. In a typical installation, the version may be visible in the application banner, in a version.properties file within the installation, or in the deployed WAR file name.
    Affected if The installed version is below 21.1.30 or below 21.4.45 (for example, 21.1.25, 21.3.10, or 20.x versions)
  2. Confirm the application is reachable over the network
    Verify that the SysAid web interface is accessible via HTTP/HTTPS at the expected hostname or IP address.
    Affected if The SysAid application is exposed on a network-accessible URL
  3. Test unauthenticated access to /wmiwizard.jsp
    Using a web browser or curl command, navigate directly to the /wmiwizard.jsp endpoint without providing any login credentials. For example: curl -I http://<server>/wmiwizard.jsp
    Affected if The request returns HTTP 200 and displays the page content or redirects to /home.jsp without requiring a login prompt
  4. Test unauthenticated access to /ConcurrentLogin.jsp
    Using a web browser or curl command, navigate directly to the /ConcurrentLogin.jsp endpoint without providing any login credentials. For example: curl -I http://<server>/ConcurrentLogin.jsp
    Affected if The request returns HTTP 200 and displays the page content or redirects to /home.jsp without requiring a login prompt

Your environment is affected if the installed SysAid version is below 21.1.30 or below 21.4.45 AND either /wmiwizard.jsp or /ConcurrentLogin.jsp can be accessed without authentication, allowing unauthorized access to authenticated areas.

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 21.1.30 / 21.4.45 or later
Fixed in 21.1.3021.4.45
Interim mitigation

Restrict access to /wmiwizard.jsp and /ConcurrentLogin.jsp by enforcing proper authentication checks on these endpoints, and apply any vendor-provided security patches for SysAid.

Recommended fix High confidence

Sysaid version 21.4.45 or later (or 21.1.30 or later if staying on the 21.1 branch)

  1. 1. Back up the current Sysaid database and configuration files before upgrading
  2. 2. Download Sysaid version 21.4.45 or later from the official Sysaid vendor website
  3. 3. Apply the upgrade to your Sysaid installation following vendor documentation
  4. 4. After upgrade, verify the vulnerability is fixed by attempting to access /wmiwizard.jsp without authentication - should require login
  5. 5. Test the full authentication flow to ensure normal login functionality works properly
  6. 6. Monitor system logs for any unauthorized access attempts
Caveat Review Sysaid release notes for any breaking changes between your current version and 21.4.45 - test in staging environment first

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

Fix this in Sysaid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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