# CVE-2018-7701: Multiple cross-site request forgery (CSRF) vulnerabilities in SecurEnvoy SecurMail before 9.2.501 allow remote attackers to hijack the authe


- **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
- **Fix available:** No
- **Published:** 14 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-66fj-rrfw-3jc9

## What is CVE-2018-7701?

CVE-2018-7701 is a medium-severity vulnerability in n/a, published on 14 Mar 2018. 

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in SecurEnvoy SecurMail before 9.2.501 allow remote attackers to hijack the authentication of arbitrary users for requests that (1) delete e-mail messages via a delete action in a request to secmail/getmessage.exe or (2) spoof arbitrary users and reply to their messages via a request to secserver/securectrl.exe.

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

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

It affects 1 product.


Products: Securenvoy Securmail.

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

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

## Is CVE-2018-7701 being exploited?

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

Public exploit code:

- SecurEnvoy SecurMail 9.1.501 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-7702](https://insights.sbomify.com/CVE-2018-7702/): Missing authorization in n/a (critical 9.1)
- [CVE-2020-13376](https://insights.sbomify.com/CVE-2020-13376/): File upload in n/a (critical 9.0)
- [CVE-2018-7705](https://insights.sbomify.com/CVE-2018-7705/): Path traversal in n/a (high 8.1)
- [CVE-2018-7704](https://insights.sbomify.com/CVE-2018-7704/): Information disclosure in n/a (medium 6.5)
- [CVE-2018-7706](https://insights.sbomify.com/CVE-2018-7706/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7701 is a medium-severity vulnerability in n/a, published on 14 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2018-7701 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-7701/ (Markdown: https://insights.sbomify.com/CVE-2018-7701/index.md)
```

## Sources

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

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