# CVE-2017-18179: Auth bypass in n/a

> Attackers can maintain unauthorized access via non-expiring tokens that persist after password changes or session termination in Sitefinity.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vm75-74f6-g8qp

## What is CVE-2017-18179?

CVE-2017-18179 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Progress Sitefinity 9.1 uses wrap_access_token as a non-expiring authentication token that remains valid after a password change or a session termination. Also, it is transmitted as a GET parameter. This is fixed in 10.1.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Progress Sitefinity.

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

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

## Is CVE-2017-18179 being exploited?

There is no known exploitation of CVE-2017-18179 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-18179 and fix it if it is affected.

What it is: CVE-2017-18179 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18179 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-18179/ (Markdown: https://insights.sbomify.com/CVE-2017-18179/index.md)
```

## Sources

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

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