dbcve.org
Service ManagerApplication · Easyvista

CVE-2022-38489

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
An issue was discovered in EasyVista 2020.2.125.3 and 2022.1.109.0.03 It is prone to stored Cross-site Scripting (XSS). Version 2022.1.110.1.02 fixes the vulnerably.

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

EasyVista versions 2020.2.125.3 and 2022.1.109.0.03 contain a stored Cross-site Scripting (XSS) vulnerability where malicious scripts can be persistently injected into the application and executed when other users view the affected content.

MitigationUpgrade to EasyVista version 2022.1.110.1.02 or later to remediate this vulnerability.

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
Service ManagerApplication
Affected:= 2020.2.125.3= 2022.1.109.0.03

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 EasyVista Service Manager version
    Locate the version information for your EasyVista Service Manager installation. This is typically found in the application administration panel, about section, or system information page. The exact location may vary based on your installation type (on-premise or cloud).
    Affected if The installed version is exactly 2020.2.125.3 or exactly 2022.1.109.0.03
  2. Check application configuration files
    If you have access to the server hosting EasyVista, examine configuration files that may contain version metadata. Look for files named version.info, about.php, or similar in the EasyVista installation directory.
    Affected if Configuration files show the version matches 2020.2.125.3 or 2022.1.109.0.03
  3. Review stored user-generated content
    Examine the database or application content management areas where users submit data that gets stored and displayed to others. This includes fields like comments, descriptions, request details, or any free-text input that other users can view.
    Affected if The application stores and displays user-submitted content without proper sanitization, allowing script tags to persist and execute when viewed by other users
  4. Verify XSS input filtering
    Test whether the application properly sanitizes or encodes HTML/script input in user-controllable fields. Submit a benign test script payload in any user-input field and check if it is rendered as plain text or executed when viewed.
    Affected if Script tags submitted in user fields are rendered as active HTML/javascript rather than being escaped or removed

You are affected if your EasyVista Service Manager version is exactly 2020.2.125.3 or exactly 2022.1.109.0.03 and the application stores and displays user content without proper input sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to EasyVista version 2022.1.110.1.02 or later to remediate this vulnerability.

Recommended fix High confidence

2022.1.110.1.02

  1. 1. Back up the current Service Manager database and all configuration files
  2. 2. Review EasyVista upgrade documentation for version 2022.1.110.1.02
  3. 3. Test the upgrade in a non-production/staging environment first
  4. 4. Apply the upgrade to production environment, upgrading to version 2022.1.110.1.02
  5. 5. Verify the XSS vulnerability is fixed by confirming the application version
  6. 6. Perform basic functional testing to ensure the upgrade was successful
Caveat No specific breaking changes mentioned in the provided advisory; standard upgrade risks apply

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

Fix this in Service Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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