CVE-2017-7692

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 32%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SquirrelMail 1.4.22 (and other versions before 20170427_0200-SVN) allows post-authentication remote code execution via a sendmail.cf file that is mishandled in a popen call. It's possible to exploit this vulnerability to execute arbitrary shell commands on the remote server. The problem is in the Deliver_SendMail.class.php with the initStream function that uses escapeshellcmd() to sanitize the sendmail command before executing it. The use of escapeshellcmd() is not correct in this case since it doesn't escape whitespaces, allowing the injection of arbitrary command parameters. The problem is in -f$envelopefrom within the sendmail command line. Hence, if the target server uses sendmail and SquirrelMail is configured to use it as a command-line program, it's possible to trick sendmail into using an attacker-provided configuration file that triggers the execution of an arbitrary command. For exploitation, the attacker must upload a sendmail.cf file as an email attachment, and inject the sendmail.cf filename with the -C option within the "Options > Personal Informations > Email Address" setting.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
32%
EPSS %ILE
98%
KEV
Not listed

Published

April 20, 2017

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated May 22, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

oss-security - Re: SquirrelMail <= 1.4.23 Remote Code Execution (CVE-2017-7692)

http://openwall.com/lists/oss-security/2017/04/27/1
generic🟡 PoC Available

oss-security - CVE-2017-7692: Squirrelmail 1.4.22 Remote Code Execution

http://openwall.com/lists/oss-security/2017/04/19/6
generic🟡 PoC Available

SquirrelMail < 1.4.22 - Remote Code Execution - Linux remote Exploit

https://www.exploit-db.com/exploits/41910/
generic

SquirrelMail: Remote Code Execution (GLSA 201709-13) — Gentoo security

https://security.gentoo.org/glsa/201709-13
generic🟡 PoC Available

SquirrelMail-Exploit-Remote-Code-Exec-CVE-2017-7692-Vuln

https://legalhackers.com/advisories/SquirrelMail-Exploit-Remote-Code-Exec-CVE-2017-7692-Vuln.html
generic
http://www.securitytracker.com/id/1038312
generic
http://www.securityfocus.com/bid/98067
generic

[SECURITY] [DSA 3852-1] squirrelmail security update

http://www.debian.org/security/2017/dsa-3852

Affected Packages

(2 across 2 ecosystems)
Debian:7(1)
PackageVulnerable rangeFixed inDependents
squirrelmail2:1.4.23~svn20120406-22:1.4.23~svn20120406-2+deb7u1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
squirrelmail2:1.4.23~svn20120406-22:1.4.23~svn20120406-2+deb8u1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-24 13:59 UTCEPSS rescore
  2. 2026-09-23 13:42 UTCEPSS rescore
  3. 2026-09-21 20:27 UTCEPSS rescore
  4. 2026-09-19 15:36 UTCEPSS rescore
  5. 2026-09-17 19:22 UTCEPSS rescore
  6. 2026-09-17 19:22 UTCEPSS rescore
  7. 2026-09-15 03:05 UTCEPSS rescore
  8. 2026-09-12 14:56 UTCEPSS rescore
  9. 2026-09-11 09:31 UTCEPSS rescore
  10. 2026-09-05 15:24 UTCEPSS rescore
  11. 2026-09-04 13:56 UTCEPSS rescore
  12. 2026-09-04 05:02 UTCEPSS rescore
  13. 2026-09-02 14:07 UTCEPSS rescore
  14. 2026-09-02 14:07 UTCEPSS rescore
  15. 2026-09-01 03:31 UTCEPSS rescore
  16. 2026-08-30 19:13 UTCEPSS rescore
  17. 2026-08-28 21:36 UTCEPSS rescore
  18. 2026-08-27 14:21 UTCEPSS rescore
  19. 2026-08-26 14:41 UTCEPSS rescore
  20. 2026-08-25 13:44 UTCEPSS rescore
  21. 2026-08-21 23:44 UTCEPSS rescore
  22. 2026-08-19 16:59 UTCEPSS rescore
  23. 2026-08-18 13:43 UTCEPSS rescore
  24. 2026-08-16 14:51 UTCEPSS rescore
  25. 2026-08-16 02:10 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:26 UTCEPSS rescore
  2. 2026-08-12 13:46 UTCEPSS rescore
  3. 2026-08-08 16:32 UTCEPSS rescore
  4. 2026-08-07 16:22 UTCEPSS rescore
  5. 2026-08-06 13:42 UTCEPSS rescore
  6. 2026-08-06 13:42 UTCEPSS rescore
  7. 2026-08-05 19:13 UTCEPSS rescore
  8. 2026-08-02 02:23 UTCEPSS rescore
  9. 2026-08-02 02:23 UTCEPSS rescore
  10. 2026-07-30 16:24 UTCEPSS rescore
  11. 2026-07-30 01:26 UTCEPSS rescore
  12. 2026-07-28 15:32 UTCEPSS rescore
  13. 2026-07-26 14:51 UTCEPSS rescore
  14. 2026-07-26 14:51 UTCEPSS rescore
  15. 2026-07-23 14:15 UTCEPSS rescore
  16. 2026-07-23 01:30 UTCEG score recompute
  17. 2026-07-22 22:10 UTCEG score recompute
  18. 2026-07-22 14:04 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-20 17:04 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-19 02:26 UTCEPSS rescore
  23. 2026-07-19 02:26 UTCEPSS rescore
  24. 2026-07-18 10:01 UTCEPSS rescore
  25. 2026-07-16 16:59 UTCEPSS rescore
  26. 2026-07-16 16:59 UTCEPSS rescore
  27. 2026-07-15 16:55 UTCEPSS rescore
  28. 2026-07-15 16:54 UTCEPSS rescore
  29. 2026-07-13 22:26 UTCEPSS rescore
  30. 2026-07-13 22:26 UTCEPSS rescore
  31. 2026-07-12 05:43 UTCEPSS rescore
  32. 2026-07-11 08:24 UTCEPSS rescore
  33. 2026-07-09 19:06 UTCEPSS rescore
  34. 2026-07-06 16:24 UTCEPSS rescore
  35. 2026-07-06 16:24 UTCEPSS rescore
  36. 2026-07-06 02:20 UTCEPSS rescore
  37. 2026-07-06 02:20 UTCEPSS rescore
  38. 2026-07-04 06:28 UTCEPSS rescore
  39. 2026-07-04 06:28 UTCEPSS rescore
  40. 2026-07-02 16:54 UTCEPSS rescore
  41. 2026-07-01 15:03 UTCEPSS rescore
  42. 2026-06-30 23:19 UTCEPSS rescore
  43. 2026-06-30 23:19 UTCEPSS rescore
  44. 2026-06-28 04:53 UTCEPSS rescore
  45. 2026-06-28 04:53 UTCEPSS rescore
  46. 2026-06-27 03:06 UTCEPSS rescore
  47. 2026-06-25 13:47 UTCEPSS rescore
  48. 2026-06-24 14:02 UTCEPSS rescore
  49. 2026-06-24 14:02 UTCEPSS rescore
  50. 2026-06-23 21:30 UTCEPSS rescore
  51. 2026-06-23 21:30 UTCEPSS rescore
  52. 2026-06-21 14:54 UTCEPSS rescore
  53. 2026-06-21 14:54 UTCEPSS rescore
  54. 2026-06-21 01:57 UTCEPSS rescore
  55. 2026-06-21 01:57 UTCEPSS rescore
  56. 2026-06-18 17:50 UTCEPSS rescore
  57. 2026-06-17 17:50 UTCEPSS rescore
  58. 2026-06-16 17:50 UTCEPSS rescore
  59. 2026-06-15 17:45 UTCEPSS rescore
  60. 2026-06-14 23:14 UTCEPSS rescore
  61. 2026-06-14 23:14 UTCEPSS rescore
  62. 2026-06-13 22:58 UTCEPSS rescore
  63. 2026-06-13 22:57 UTCEPSS rescore
  64. 2026-06-12 23:09 UTCEPSS rescore
  65. 2026-06-12 23:09 UTCEPSS rescore
  66. 2026-06-11 13:57 UTCEPSS rescore
  67. 2026-06-10 22:15 UTCEPSS rescore
  68. 2026-06-10 13:19 UTCEPSS rescore
  69. 2026-06-08 14:14 UTCEPSS rescore
  70. 2026-06-08 14:14 UTCEPSS rescore
  71. 2026-06-07 15:22 UTCEPSS rescore
  72. 2026-06-07 15:22 UTCEPSS rescore
  73. 2026-06-05 22:44 UTCEPSS rescore
  74. 2026-06-05 22:44 UTCEPSS rescore
  75. 2026-06-05 06:08 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-41910
    First seen Apr 23, 2017

    SquirrelMail < 1.4.22 - Remote Code Execution

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-7692?
CVE-2017-7692 is a high vulnerability published on April 20, 2017. SquirrelMail 1.4.22 (and other versions before 201704270200-SVN) allows post-authentication remote code execution via a sendmail.cf file that is mishandled in a popen call. It's possible to exploit this vulnerability to execute arbitrary shell commands on the remote server. The problem is in the…
When was CVE-2017-7692 disclosed?
CVE-2017-7692 was first published in the National Vulnerability Database on April 20, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-7692 actively exploited?
CVE-2017-7692 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32% probability of exploitation in the next 30 days, which ranks it in the top 1.7% of all scored CVEs.
What is the CVSS score of CVE-2017-7692?
CVE-2017-7692 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-7692?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7692, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-7692

Explore →

Is Your Infrastructure Affected by CVE-2017-7692?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs