dbcve.org
Sysaid On PremisesApplication · Sysaid

CVE-2023-32225

HIGH · 7.2 CVSS v3.1 Published 2023-07-30
Fix available
A fix is available. Upgrade to 23.2.14 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 - CWE-434: Unrestricted Upload of File with Dangerous Type -  A malicious user with administrative privileges may be able to upload a dangerous filetype via an unspecified method.

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 unrestricted file upload vulnerability (CWE-434) in Sysaid ITSM software where an authenticated administrative user can upload dangerous file types through an unspecified upload mechanism. Successful exploitation could allow execution of malicious code if executable files (such as .jsp, .exe, .php, or .asp) are uploaded and subsequently accessed via the web server.

MitigationImplement strict file type validation using a whitelist approach, restrict executable extensions, store uploaded files outside the webroot, and disable script execution in upload directories. Consider adding content-type and magic byte validation in addition to extension checking.

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
Sysaid On PremisesApplication
Affected:< 23.2.14

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

CVSS:3.1/AV:N/AC:L/PR:H/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
    Access the Sysaid On Premises admin console or check system documentation for the current version number. This is typically visible in the About or System Info section of the administration interface.
    Affected if The installed version is below 23.2.14 (any version < 23.2.14 is affected)
  2. Verify administrative access to file upload functionality
    Confirm that authenticated administrator accounts exist and can access file upload features within the Sysaid platform (such as attachment uploads in tickets, document management, or asset management modules).
    Affected if Administrative users with upload capabilities are present and the upload mechanism is accessible to them
  3. Determine upload storage location
    Inspect the Sysaid configuration to identify where uploaded files are stored - check if the upload directory is within the webroot (web-accessible directory) or stored outside the public web directory structure.
    Affected if Uploaded files are stored in a web-accessible directory within the webroot
  4. Check script execution controls on upload directories
    Review the web server or Sysaid configuration to determine if script execution is disabled in the directory where uploaded files are stored. Check for restrictions on executable file types (.jsp, .php, .asp, .exe).
    Affected if Script execution is NOT disabled in the upload directory and executable file types are permitted
  5. Confirm dangerous file type acceptance
    Test or review the file upload mechanism to verify whether the system accepts potentially dangerous extensions such as .jsp, .exe, .php, or .asp without sufficient validation.
    Affected if The upload mechanism accepts and allows storage of executable file types (.jsp, .php, .asp, .exe)

A system is affected if it runs Sysaid On Premises version < 23.2.14 AND allows authenticated admins to upload executable files (.jsp, .exe, .php, .asp) to a web-accessible location where script execution is not disabled.

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.2.14 or later
Fixed in 23.2.14
Interim mitigation

Implement strict file type validation using a whitelist approach, restrict executable extensions, store uploaded files outside the webroot, and disable script execution in upload directories. Consider adding content-type and magic byte validation in addition to extension checking.

Recommended fix Moderate confidence

23.2.14

  1. Verify current Sysaid On Premises version in use
  2. Review Sysaid upgrade documentation for version 23.2.14
  3. Create a full backup of the current Sysaid installation and database
  4. Schedule a maintenance window for the upgrade
  5. Download Sysaid On Premises version 23.2.14 or later from the official vendor portal
  6. Execute the upgrade following Sysaid's standard upgrade procedure
  7. Verify the upgrade was successful by checking the version number
  8. Test that file upload functionality works correctly with proper file type restrictions

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

Fix this in Sysaid On Premises 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-2023-32225 — 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-32225 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