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

> Cross-site scripting vulnerability in WP Statistics plugin allows attackers to inject malicious scripts via referrer page parameters.

- **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:** 7 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j457-cgr7-vf3m

## What is CVE-2017-10991?

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

The WP Statistics plugin through 12.0.9 for WordPress has XSS in the rangestart and rangeend parameters on the wps_referrers_page page.

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

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

It affects 1 product.


Products: Wp-Statistics Wp Statistics.

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

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

## Is CVE-2017-10991 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-2135](https://insights.sbomify.com/CVE-2017-2135/): Cross-site scripting in WP Statistics (medium 6.1)
- [CVE-2017-2147](https://insights.sbomify.com/CVE-2017-2147/): Cross-site scripting in WP Statistics (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10991 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Jul 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: There is no known exploitation of CVE-2017-10991 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-10991/ (Markdown: https://insights.sbomify.com/CVE-2017-10991/index.md)
```

## Sources

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

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