dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Dec 2023. Known ransomware use
SysaidApplication

CVE-2023-47246

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-10
Fix available
A fix is available. Upgrade to 23.3.36 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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
In SysAid On-Premise before 23.3.36, a path traversal vulnerability leads to code execution after an attacker writes a file to the Tomcat webroot, as exploited in the wild in November 2023.

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

A path traversal vulnerability in SysAid On-Premise versions before 23.3.36 allows authenticated or unauthenticated attackers to write arbitrary files to the Tomcat webroot directory, enabling remote code execution via deployed web shells or malicious JSP files. This vulnerability was actively exploited in the wild in November 2023.

MitigationUpgrade SysAid On-Premise to version 23.3.36 or later to remediate the path traversal vulnerability; if immediate patching is not possible, restrict network access to the SysAid server and monitor for suspicious web requests and new files in the webroot.

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:< 23.3.36

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 SysAid version
    Locate the installed SysAid On-Premise version number. This is typically displayed on the login page footer, in the SysAid admin console under System Information, or in the installation directory in a version file. Compare this version to the affected range of versions prior to 23.3.36.
    Affected if The installed version is any release before 23.3.36, including older major versions.
  2. Confirm Tomcat deployment
    Determine whether the SysAid application is deployed on a Tomcat application server. This is commonly the default for SysAid On-Premise installations. Check for the presence of a Tomcat installation directory and confirm SysAid is running as a web application on Tomcat.
    Affected if SysAid is running on Tomcat as the application server, as the vulnerability specifically allows writing files to the Tomcat webroot directory.
  3. Inspect Tomcat webroot for unexpected files
    Examine the Tomcat webroot directory (typically the 'webapps/ROOT' or 'webapps/sysaid' folder) for newly created or modified files. Look for unfamiliar JSP files, scripts, or executables that were not part of a legitimate SysAid installation. Pay particular attention to files with extensions such as .jsp, .jspx, .asp, .php, or .exe in the webroot.
    Affected if Unexpected files exist in the webroot, especially executable files or webshells that were not intentionally deployed.
  4. Review web access logs for path traversal patterns
    Analyze Tomcat or SysAid access logs for suspicious requests containing path traversal sequences. Look for HTTP requests with patterns such as '..\..\' or '../' directed toward upload or file handling endpoints, particularly those that may indicate attempts to write files to the webroot.
    Affected if Log analysis reveals path traversal requests or anomalous file write attempts to the webroot directory.

You are affected if your SysAid On-Premise version is below 23.3.36 and the application is deployed on Tomcat, especially if unexpected files are found in the webroot or suspicious path traversal requests appear in logs.

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

Upgrade SysAid On-Premise to version 23.3.36 or later to remediate the path traversal vulnerability; if immediate patching is not possible, restrict network access to the SysAid server and monitor for suspicious web requests and new files in the webroot.

Recommended fix High confidence

SysAid On-Premise 23.3.36 or later

  1. Upgrade SysAid On-Premise to version 23.3.36 or later to remediate the path traversal vulnerability
  2. After upgrading, verify the Tomcat webroot does not contain any malicious files placed by attackers
  3. Check for indicators of compromise as this vulnerability was exploited in the wild in November 2023

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

Fix this in Sysaid Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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-2023-47246 — 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-2023-47246 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