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

> Cross-site scripting in Sitefinity allows attackers to inject scripts via user profile fields, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6hwr-p935-p8mg

## What is CVE-2017-18177?

CVE-2017-18177 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Progress Sitefinity 9.1 has XSS via the Last name, First name, and About fields on the New User Creation Page. This is fixed in 10.1.

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

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

It affects 1 product.


Products: Progress Sitefinity.

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

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

## Is CVE-2017-18177 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9248](https://insights.sbomify.com/CVE-2017-9248/): Progress Telerik UI for ASP.NET AJAX and Sitefinity Cryptographic Weakness (critical 9.8, exploited in the wild)
- [CVE-2026-7312](https://insights.sbomify.com/CVE-2026-7312/): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity (critical 10.0)
- [CVE-2026-7198](https://insights.sbomify.com/CVE-2026-7198/): CWE-284: Improper Access Control in web services in Progress Sitefinity (critical 9.8)
- [CVE-2023-29375](https://insights.sbomify.com/CVE-2023-29375/): File upload in n/a (critical 9.8)
- [CVE-2019-17392](https://insights.sbomify.com/CVE-2019-17392/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18177 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-18177 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-18177/ (Markdown: https://insights.sbomify.com/CVE-2017-18177/index.md)
```

## Sources

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

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