# CVE-2022-4235: Cross-site scripting in RushBet

> Remote attackers can steal customer accounts in the RushBet mobile app by exploiting improper data validation in an exposed activity.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 18 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-2cfq-hfxh-5h78

## What is CVE-2022-4235?

CVE-2022-4235 is a medium-severity cross-site scripting vulnerability in RushBet, published on 18 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

RushBet version 2022.23.1-b490616d allows a remote attacker to steal customer accounts via use of a malicious application. This is possible because the application exposes an activity and does not properly validate the data it receives.

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

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

It affects 1 product.


Products: Rushstreetinteractive Rushbet.

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

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

## Is CVE-2022-4235 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4235 is a medium-severity cross-site scripting vulnerability in RushBet, published on 18 Jan 2023. 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-4235 exists.

Affected product: RushBet. 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-4235/ (Markdown: https://insights.sbomify.com/CVE-2022-4235/index.md)
```

## Sources

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

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