Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2018-7701: CSRF in SecurEnvoy SecurMail <9.2.501

Published Mar 14, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS2.9%87th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Securenvoy
IdentifiersCVE-2018-7701CWE-352 · Cross-Site Request Forgery (CSRF)

CVE-2018-7701 describes multiple cross-site request forgery (CSRF) vulnerabilities in SecurEnvoy SecurMail versions prior to 9.2.501. The vulnerabilities allow remote attackers to perform actions on behalf of authenticated users without their consent. Specifically, attackers can (1) delete e-mail messages by sending a crafted request to secmail/getmessage.exe with a delete action, or (2) spoof arbitrary users and reply to their messages via crafted requests to secserver/securectrl.exe. The vulnerabilities stem from insufficient validation of user requests and lack of anti-CSRF protections in the affected endpoints.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to hijack the authentication of arbitrary users, leading to unauthorized deletion of e-mail messages or sending of spoofed replies as other users. This can result in loss of important communications, unauthorized message manipulation, and potential reputational or legal consequences for organizations relying on SecurMail for secure messaging.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict access to the SecurMail web interface to trusted networks, educate users to avoid clicking on suspicious links while authenticated, and consider implementing web application firewall (WAF) rules to detect and block suspicious requests targeting the vulnerable endpoints.

Remediation

Patch, then assume compromise.

Upgrade SecurEnvoy SecurMail to version 9.2.501 or later, where these CSRF vulnerabilities have been addressed. Ensure all endpoints are protected with proper anti-CSRF mechanisms and validate user actions appropriately.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SecurenvoySecurmailapplication
FAQ

Frequently asked questions

Is CVE-2018-7701 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2018-7701 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2018-7701?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2018-7701.
Is there a patch for CVE-2018-7701?
Upgrade SecurEnvoy SecurMail to version 9.2.501 or later, where these CSRF vulnerabilities have been addressed. Ensure all endpoints are protected with proper anti-CSRF mechanisms and validate user actions appropriately.
What products are affected by CVE-2018-7701?
Securenvoy Securmail.
How severe is CVE-2018-7701?
CVE-2018-7701 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 2.9% (87th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.