CVE-2023-5966: EspoCRM · Unrestricted File Upload
Affects EspoCRMSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| EspoCRM EspoCRM | Affected
| Fixed in– |
AI-suggested
European organizations should immediately verify their EspoCRM version and upgrade to a patched version once available from the vendor. In the absence of an official patch, organizations should restrict access to the extension deployment form to only the most trusted administrators and monitor for any unusual upload activity. Implement strict file upload validation controls at the web application firewall (WAF) or reverse proxy level to block ZIP files containing executable PHP scripts or other dangerous content. Employ network segmentation to isolate EspoCRM servers from critical internal systems to limit lateral movement in case of compromise. Conduct regular audits of user privileges to ensure that only necessary personnel have high-level access. Enable comprehensive logging and real-time alerting on file upload events and administrative actions within EspoCRM. Additionally, organizations should consider deploying runtime application self-protection (RASP) solutions to detect and block malicious code execution attempts. Finally, prepare an incident response plan specifically addressing web application compromise scenarios involving EspoCRM.
Description
An authenticated privileged attacker could upload a specially crafted zip to the EspoCRM server in version 7.2.5, via the extension deployment form, which could lead to arbitrary PHP code execution.