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

> Cross-site scripting vulnerability in the amtyThumb posts WordPress plugin allows attackers to inject malicious scripts via the query string.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 29 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rcmg-qqg5-w3f3

## What is CVE-2017-17059?

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

XSS exists in the amtyThumb amty-thumb-recent-post (aka amtyThumb posts or wp-thumb-post) plugin 8.1.3 for WordPress via the query string to amtyThumbPostsAdminPg.php.

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

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

It affects 1 product.


Products: Amtythumb Project Amtythumb.

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

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

## Is CVE-2017-17059 being exploited?

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

Public exploit code:

- WordPress amtyThumb Posts 8.1.3 - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-17059.yaml

## Other vulnerabilities in n/a

- [CVE-2022-1683](https://insights.sbomify.com/CVE-2022-1683/): amtyThumb <= 4.2.0 - Subscriber+ SQLi (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17059 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Nov 2017. 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-2017-17059 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-2017-17059/ (Markdown: https://insights.sbomify.com/CVE-2017-17059/index.md)
```

## Sources

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

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