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

> Cross-site scripting vulnerability in the Raygun for WordPress plugin allows attackers to inject malicious scripts into the settings interface.

- **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-vc9h-6cr4-9jh7

## What is CVE-2017-18531?

CVE-2017-18531 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 raygun4wp plugin before 1.8.3 for WordPress has XSS in the settings, a different issue than CVE-2017-9288.

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

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

It affects 1 product.


Products: Raygun Raygun4wp.

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

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

## Is CVE-2017-18531 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9288](https://insights.sbomify.com/CVE-2017-9288/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18531 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: There is no known exploitation of CVE-2017-18531 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-18531/ (Markdown: https://insights.sbomify.com/CVE-2017-18531/index.md)
```

## Sources

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

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