# CVE-2022-50896: Testa 3.5.1 Online Test Management System - Reflected Cross-Site Scripting (XSS)

> Attackers can inject malicious JavaScript via the login redirect parameter, allowing arbitrary script execution in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/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:** 1 Oct 2026
- **Also known as:** GHSA-j8c8-7496-m39v

## What is CVE-2022-50896?

CVE-2022-50896 is a medium-severity cross-site scripting vulnerability in Testa, 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

Testa 3.5.1 contains a reflected cross-site scripting vulnerability in the login.php redirect parameter that allows attackers to inject malicious scripts. Attackers can craft a specially encoded payload in the redirect parameter to execute arbitrary JavaScript in victim's browser context.

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

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


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

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

## Is CVE-2022-50896 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50896 is a medium-severity cross-site scripting vulnerability in Testa, 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-50896 exists.

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

## Sources

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

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