# CVE-2018-10232: Cross-site request forgery in n/a

> Remote attackers can hijack authenticated user sessions to obtain sensitive information via CSRF in TOPdesk.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 11 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j2pm-9g69-p32r

## What is CVE-2018-10232?

CVE-2018-10232 is a medium-severity vulnerability in n/a, published on 11 Jul 2018. 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 TOPdesk before 8.05.017 (June 2018 version) and before 5.7.SR9 allows remote attackers to hijack the authentication of authenticated users for requests that can obtain sensitive information via unspecified vectors.

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

## Which versions are affected by CVE-2018-10232?

It affects 1 product.


Products: Topdesk Topdesk.

## How do I fix CVE-2018-10232?

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

## Is CVE-2018-10232 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34923](https://insights.sbomify.com/CVE-2023-34923/): Auth bypass in n/a (high 8.1)
- [CVE-2018-10231](https://insights.sbomify.com/CVE-2018-10231/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-7276](https://insights.sbomify.com/CVE-2017-7276/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10232 and fix it if it is affected.

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

## Sources

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

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