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

> Remote attackers can hijack user sessions to modify settings, send emails, or change contacts due to missing CSRF tokens in Totemomail Encryption Gateway.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 20 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pwp9-wc2j-35m6

## What is CVE-2018-6563?

CVE-2018-6563 is a high-severity vulnerability in n/a, published on 20 Jun 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

Multiple cross-site request forgery (CSRF) vulnerabilities in totemomail Encryption Gateway before 6.0.0_Build_371 allow remote attackers to hijack the authentication of users for requests that (1) change user settings, (2) send emails, or (3) change contact information by leveraging lack of an anti-CSRF token.

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

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

It affects 1 product.


Products: Totemo Encryption Gateway.

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

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

## Is CVE-2018-6563 being exploited?

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

Public exploit code:

- totemomail Encryption Gateway 6.0.0 Build 371 - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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