# CVE-2017-20167: Minichan reports.php cross site scripting

> Remote attackers can inject malicious scripts via the headline argument in reports.php, potentially executing code in victim browsers.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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:** 14 Jan 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q257-jh5g-vh5c

## What is CVE-2017-20167?

CVE-2017-20167 is a low-severity cross-site scripting vulnerability in Minichan, published on 14 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

A vulnerability, which was classified as problematic, was found in Minichan. This affects an unknown part of the file reports.php. The manipulation of the argument headline leads to cross site scripting. It is possible to initiate the attack remotely. The identifier of the patch is fc0e732e58630cba318d6bf49d1388a7aa9d390e. It is recommended to apply a patch to fix this issue. The identifier VDB-217785 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2017-20167?

It affects 1 product.


Products: Minichan Minichan.

## How do I fix CVE-2017-20167?

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

## Is CVE-2017-20167 being exploited?

There is no known exploitation of CVE-2017-20167 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20167 and fix it if it is affected.

What it is: CVE-2017-20167 is a low-severity cross-site scripting vulnerability in Minichan, published on 14 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: There is no known exploitation of CVE-2017-20167 in the wild and no public exploit code.

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

## Sources

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

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