{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36277 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36277 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36277 is a medium-severity cross-site scripting vulnerability in TCMAN GIM, published on 4 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-36277 and fix it if it is affected.\n\nWhat it is: CVE-2022-36277 is a medium-severity cross-site scripting vulnerability in TCMAN GIM, published on 4 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-36277 in the wild and no public exploit code.\n\nAffected product: TCMAN GIM. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-36277/ (Markdown: https://insights.sbomify.com/CVE-2022-36277/index.md)","id":"CVE-2022-36277","markdown":"https://insights.sbomify.com/CVE-2022-36277/index.md","name":"CVE-2022-36277","record":{"aliases":["GHSA-g2hx-67cj-4mvm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TCMAN GIM","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts via specific parameters in TCMAN GIM, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"gim","vendor":"tcman"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection vulnerability in TCMAN GIM","id":"CVE-2022-36277","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Intel(R) Battery Life Diagnostic Tool software","id":"CVE-2022-36278"},"packages":[],"prev":{"headline":"SQL injection vulnerability in TCMAN GIM","id":"CVE-2022-36276"},"products":["GIM"],"published":"2023-10-04","related":[{"cvss_score":10,"headline":"TCMAN GIM SQL injection vulnerability","id":"CVE-2021-40850","kev_date_added":null,"published":"2021-12-17"},{"cvss_score":9.9,"headline":"SQL injection vulnerability in TCMAN GIM","id":"CVE-2022-36276","kev_date_added":null,"published":"2023-10-04"},{"cvss_score":9.3,"headline":"Missing authentication vulnerability in TCMAN GIM v11","id":"CVE-2025-40664","kev_date_added":null,"published":"2025-05-26"},{"cvss_score":9.3,"headline":"Multiple vulnerabilities in TCMAN's GIM","id":"CVE-2025-40620","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.3,"headline":"Multiple vulnerabilities in TCMAN's GIM","id":"CVE-2025-40621","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.3,"headline":"Multiple vulnerabilities in TCMAN's GIM","id":"CVE-2025-40622","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":9.3,"headline":"Multiple vulnerabilities in TCMAN's GIM","id":"CVE-2025-40623","kev_date_added":null,"published":"2025-05-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-05","vendors":["TCMAN"]},"summary":"Attackers can inject malicious scripts via specific parameters in TCMAN GIM, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2022-36277/"}