# CVE-2022-42187: Cross-site scripting in n/a

> Cross-site scripting in Hustoj admin panel allows attackers to execute arbitrary scripts, potentially compromising administrator accounts.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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:** 17 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-6x38-jqg6-xx78

## What is CVE-2022-42187?

CVE-2022-42187 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Nov 2022. 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

Hustoj 22.09.22 has a XSS Vulnerability in /admin/problem_judge.php.

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

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

It affects 1 product.


Products: Hustoj Hustoj.

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

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

## Is CVE-2022-42187 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-24479](https://insights.sbomify.com/CVE-2026-24479/): HUSTOJ has Arbitrary File Write (Zip Slip) in Problem Import Modules that leads to RCE (critical 9.3)
- [CVE-2025-50938](https://insights.sbomify.com/CVE-2025-50938/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2026-23873](https://insights.sbomify.com/CVE-2026-23873/): HUSTOJ is Vulnerable to Stored CSV Injection (Formula Injection) in Contest Rank Export (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42187 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 Nov 2022. 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-42187 exists.

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

## Sources

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

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