# CVE-2017-2097: Cross-site request forgery in Knowledge

> Remote attackers can hijack administrator authentication in Knowledge CMS via CSRF, requiring an upgrade to secure the application.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 28 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j597-mqj3-79c6

## What is CVE-2017-2097?

CVE-2017-2097 is a high-severity vulnerability in support-project.org Knowledge, published on 28 Apr 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 request forgery (CSRF) vulnerability in Knowledge versions prior to v1.7.0 allows remote attackers to hijack the authentication of administrators via unspecified vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Support-Project Knowledge.

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

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

## Is CVE-2017-2097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2097 is a high-severity vulnerability in support-project.org Knowledge, published on 28 Apr 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-2097 in the wild and no public exploit code.

Affected product: support-project.org Knowledge. 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-2097/ (Markdown: https://insights.sbomify.com/CVE-2017-2097/index.md)
```

## Sources

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

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