{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50952 exists.","fix":"No fix has been published for CVE-2022-50952 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-50952 is a medium-severity cross-site scripting vulnerability in Banco Guayaquil, published on 1 Feb 2026. 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-50952 and fix it if it is affected.\n\nWhat it is: CVE-2022-50952 is a medium-severity cross-site scripting vulnerability in Banco Guayaquil, published on 1 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50952 exists.\n\nAffected product: Banco Guayaquil. 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-50952/ (Markdown: https://insights.sbomify.com/CVE-2022-50952/index.md)","id":"CVE-2022-50952","markdown":"https://insights.sbomify.com/CVE-2022-50952/index.md","name":"CVE-2022-50952","record":{"aliases":["GHSA-c5gw-crjf-j6m8"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Banking mobile app","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts via profile name input in the Banco Guayaquil iOS app, leading to code execution and data theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Banco Guayaquil 8.0.0 mobile iOS application contains a persistent cross-site scripting vulnerability in the TextBox Name Profile input. Attackers can inject malicious script code through a POST request that executes on application review without user interaction.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Banco Guayaquil 8.0.0 Mobile iOS Cross-Site Scripting via Profile Name Input","id":"CVE-2022-50952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"WordPress Plugin admin-word-count-column 2.2 Local File Read","id":"CVE-2022-50953"},"packages":[],"prev":{"headline":"WiFi File Transfer 1.0.8 Persistent XSS via Web Server Input Validation","id":"CVE-2022-50951"},"products":["Banco Guayaquil"],"published":"2026-02-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-02","vendors":["Banco de Guayaquil"]},"summary":"Attackers can inject malicious scripts via profile name input in the Banco Guayaquil iOS app, leading to code execution and data theft.","url":"https://insights.sbomify.com/CVE-2022-50952/"}