# CVE-2022-50952: Banco Guayaquil 8.0.0 Mobile iOS Cross-Site Scripting via Profile Name Input

> Attackers can inject malicious scripts via profile name input in the Banco Guayaquil iOS app, leading to code execution and data theft.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-c5gw-crjf-j6m8

## What is CVE-2022-50952?

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.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-50952?


## How do I fix CVE-2022-50952?

No fix has been published for CVE-2022-50952 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-50952 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50952 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50952 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-50952 exists.

Affected product: Banco Guayaquil. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50952/ (Markdown: https://insights.sbomify.com/CVE-2022-50952/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50952
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50952
- OSV: https://osv.dev/vulnerability/CVE-2022-50952

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50952/
Summaries are generated and may contain mistakes; the official description above is the record.