# CVE-2022-50925: Prowise Reflect v1.0.9 - Remote Keystroke Injection

> Attackers can inject keystrokes via WebSocket to execute arbitrary commands and open applications in Prowise Reflect.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-cj53-rx7h-6vm4

## What is CVE-2022-50925?

CVE-2022-50925 is a high-severity vulnerability in Prowise Reflect, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Prowise Reflect version 1.0.9 contains a remote keystroke injection vulnerability that allows attackers to send keyboard events through an exposed WebSocket on port 8082. Attackers can craft malicious web pages to inject keystrokes, opening applications and typing arbitrary text by sending specific WebSocket messages.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Prowise Reflect.

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

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

## Is CVE-2022-50925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50925 is a high-severity vulnerability in Prowise Reflect, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, 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-50925 exists.

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

## Sources

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

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