dbcve.org
SysaidApplication

CVE-2022-23166

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-12
Fix available
A fix is available. Upgrade to 22.1.64 / 22.2.20 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 Local File Inclusion (LFI) – An unauthenticated attacker can access to the system by accessing to "/lib/tinymce/examples/index.html" path. in the "Insert/Edit Embedded Media" window Choose Type : iFrame and File/URL : [here is the LFI] Solution: Update to 22.2.20 cloud version, or to 22.1.64 on premise version.

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

Sysaid contains a Local File Inclusion (LFI) vulnerability in the tinymce editor component. An unauthenticated attacker can exploit the 'Insert/Edit Embedded Media' feature by selecting iFrame type and providing a file path to read arbitrary files from the server filesystem, potentially exposing sensitive system data or credentials.

MitigationApply the vendor-supplied patches by updating to version 22.2.20 for cloud deployments or 22.1.64 for on-premise installations. Until patched, restrict network access to the /lib/tinymce/ path as a compensating control.

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:< 22.1.64< 22.2.20

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 version information for your Sysaid installation, typically found in the application header, about page, or version configuration file. Compare the installed version number against the affected ranges: version 22.1.64 or higher for on-premise, or version 22.2.20 or higher for cloud deployments.
    Affected if The installed version is below 22.1.64 (on-premise) or below 22.2.20 (cloud)
  2. Confirm tinymce editor is exposed
    Verify that the /lib/tinymce/ path is accessible on your Sysaid server by attempting to access this endpoint via HTTP/HTTPS from an authorized internal location.
    Affected if The /lib/tinymce/ path returns a valid response, indicating the tinymce editor component is exposed and potentially reachable over the network
  3. Check Insert/Edit Embedded Media feature
    Log into Sysaid and navigate to any area where the tinymce rich text editor is available (such as ticket descriptions, knowledge base articles, or system notes). Access the media insertion feature to verify whether the 'Insert/Edit Embedded Media' option with iFrame type selection is present and functional.
    Affected if The Insert/Edit Embedded Media feature with iFrame option is available and operational in the tinymce editor

You are affected if your Sysaid version is below 22.1.64 (on-premise) or below 22.2.20 (cloud), the tinymce editor at /lib/tinymce/ is network-accessible, and the Insert/Edit Embedded Media feature with iFrame option is enabled.

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.64 / 22.2.20 or later
Fixed in 22.1.6422.2.20
Interim mitigation

Apply the vendor-supplied patches by updating to version 22.2.20 for cloud deployments or 22.1.64 for on-premise installations. Until patched, restrict network access to the /lib/tinymce/ path as a compensating control.

Recommended fix High confidence

22.1.64 (on-premise) or 22.2.20 (cloud)

  1. Identify whether you are using Sysaid cloud or on-premise installation
  2. For on-premise installations: Upgrade Sysaid to version 22.1.64 or later
  3. For cloud installations: Upgrade Sysaid to version 22.2.20 or later
  4. After upgrading, verify the vulnerability is resolved by attempting to access the /lib/tinymce/examples/index.html path (it should not expose local files)

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

Fix this in Sysaid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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