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

> Multiple XSS vulnerabilities in the user-role plugin allow attackers to inject scripts, potentially leading to session hijacking or malicious actions.

- **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:** 20 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fqp5-3423-m5fr

## What is CVE-2017-18566?

CVE-2017-18566 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Aug 2019. 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 user-role plugin before 1.5.6 for WordPress has multiple XSS issues.

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

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

It affects 1 product.


Products: Bestwebsoft User Role.

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

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

## Is CVE-2017-18566 being exploited?

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

Public exploit code:

- User Role by BestWebSoft < 1.5.6 - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-18566.yaml

## Other vulnerabilities in n/a

- [CVE-2023-0820](https://insights.sbomify.com/CVE-2023-0820/): User Role by BestWebSoft < 1.6.7 - Privilege Escalation via CSRF (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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