# CVE-2017-8848: Cross-site request forgery in n/a

> Allen Disk allows attackers to change user passwords via Cross-Site Request Forgery, potentially leading to account takeover.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:** 8 May 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-f8qx-xf75-phhp

## What is CVE-2017-8848?

CVE-2017-8848 is a medium-severity vulnerability in n/a, published on 8 May 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

Allen Disk 1.6 has CSRF in setpass.php with an impact of changing a password.

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

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

It affects 1 product.


Products: Allen Disk Project Allen Disk.

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

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

## Is CVE-2017-8848 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9090](https://insights.sbomify.com/CVE-2017-9090/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-9091](https://insights.sbomify.com/CVE-2017-9091/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-9307](https://insights.sbomify.com/CVE-2017-9307/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2017-8832](https://insights.sbomify.com/CVE-2017-8832/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-9249](https://insights.sbomify.com/CVE-2017-9249/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8848 is a medium-severity vulnerability in n/a, published on 8 May 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-8848 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-8848/ (Markdown: https://insights.sbomify.com/CVE-2017-8848/index.md)
```

## Sources

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

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