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

> Cross-site scripting in the wp-noexternallinks plugin allows attackers to inject malicious scripts via date parameters, potentially compromising admin sessions.

- **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:** 24 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v626-c9xh-rhf4

## What is CVE-2017-15863?

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

Cross Site Scripting (XSS) exists in the wp-noexternallinks plugin before 3.5.19 for WordPress via the date1 or date2 parameter to wp-admin/options-general.php.

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

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

It affects 1 product.


Products: Wp No External Links Project Wp No External Links.

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

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

## Is CVE-2017-15863 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-26537](https://insights.sbomify.com/CVE-2023-26537/): WordPress WP No External Links Plugin <= 1.0.2 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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