# CVE-2017-16635: Cross-site scripting in n/a

> Remote attackers with low-privilege backend access can inject malicious scripts into TinyWebGallery item listings via POST requests.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 6 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pgrm-x6jp-37f9

## What is CVE-2017-16635?

CVE-2017-16635 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In TinyWebGallery v2.4, an XSS vulnerability is located in the `mkname`, `mkitem`, and `item` parameters of the `Add/Create` module. Remote attackers with low-privilege user accounts for backend access are able to inject malicious script codes into the `TWG Explorer` item listing. The request method to inject is POST and the attack vector is located on the application-side of the service. The injection point is the add/create input field and the execution point occurs in the item listing after the add or create.

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

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

It affects 1 product.


Products: Tinywebgallery Tinywebgallery.

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

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

## Is CVE-2017-16635 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-53922](https://insights.sbomify.com/CVE-2023-53922/): TinyWebGallery v2.5 Remote Code Execution via Unrestricted File Upload (critical 9.3)
- [CVE-2012-5347](https://insights.sbomify.com/CVE-2012-5347/): Command injection in n/a (high 7.5)
- [CVE-2006-4166](https://insights.sbomify.com/CVE-2006-4166/): Code injection in n/a (high 7.5)
- [CVE-2012-2931](https://insights.sbomify.com/CVE-2012-2931/): Code injection in n/a (high 7.2)
- [CVE-2012-2930](https://insights.sbomify.com/CVE-2012-2930/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16635 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2017. 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-16635 in the wild and no public exploit code.

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

## Sources

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

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