dbcve.org
GimApplication · Tcman

CVE-2022-36277

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

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
The 'sReferencia', 'sDescripcion', 'txtCodigo' and 'txtDescripcion' parameters, in the frmGestionStock.aspx and frmEditServicio.aspx files in TCMAN GIM v8.0.1, could allow an attacker to perform persistent XSS attacks.

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

TCMAN GIM v8.0.1 contains a persistent XSS vulnerability where the 'sReferencia', 'sDescripcion', 'txtCodigo', and 'txtDescripcion' parameters in frmGestionStock.aspx and frmEditServicio.aspx do not properly sanitize user input, allowing malicious scripts to be stored and executed when other users view the affected pages.

MitigationImplement proper input validation and output encoding for all user-supplied parameters. Use context-appropriate encoding (HTML entity encoding for displayed text) and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

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
GimApplication
Affected:= 8.0.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify TCMAN GIM version
    Locate the TCMAN GIM installation directory and check the version information, typically found in an About page, version file, or the application assembly/dll properties. Alternatively, access the application's login or main page and look for version information in the footer or help section.
    Affected if The installed version is exactly 8.0.1
  2. Confirm presence of affected ASPX pages
    Check if frmGestionStock.aspx and frmEditServicio.aspx exist in the TCMAN GIM web application directory. These files are typically located in the /GestionStock/ or /Servicios/ subdirectories of the web application root.
    Affected if Both frmGestionStock.aspx and frmEditServicio.aspx are present in the web application
  3. Identify if the vulnerable parameters accept user input
    Access frmGestionStock.aspx and locate input fields named 'sReferencia' and 'sDescripcion'. Access frmEditServicio.aspx and locate input fields named 'txtCodigo' and 'txtDescripcion'. These are form parameters that accept user-supplied data for stock management and service description functions.
    Affected if These four parameter fields exist and accept user input on the respective pages
  4. Test for lack of input sanitization
    Submit a benign XSS test payload such as <script>alert('XSS')</script> or <img src=x onerror=alert('XSS')> in each of the affected parameters (sReferencia, sDescripcion, txtCodigo, txtDescripcion). Then view the submitted data again or have another user view it to see if the script executes.
    Affected if The submitted script tags render as literal text or execute when the data is displayed back, indicating lack of proper output encoding

You are affected if TCMAN GIM version 8.0.1 is installed and the web application accepts and displays user input in the sReferencia, sDescripcion, txtCodigo, or txtDescripcion parameters without sanitizing HTML/script content.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all user-supplied parameters. Use context-appropriate encoding (HTML entity encoding for displayed text) and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

Fix this in Gim Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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