dbcve.org
EspocrmApplication

CVE-2023-5966

HIGH · 7.2 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 7.5.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In EspoCRM 7.2.5, the extension deployment feature allows authenticated privileged users to upload zip archives. The system fails to properly validate the contents of uploaded zip files before extraction, allowing an attacker to craft a malicious zip containing PHP files that can be written to executable locations on the server, leading to arbitrary PHP code execution.

MitigationRestrict extension deployment permissions to minimal necessary admin users, implement strict validation of zip file contents (whitelist allowed file types, prevent path traversal, block PHP file uploads), and consider disabling the extension deployment feature until official patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EspocrmApplication
Affected:<= 7.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EspoCRM installation and version
    Locate the EspoCRM installation and check the version number. Common locations include the admin panel under 'About' or by examining version files in the installation directory.
    Affected if The installed version is 7.5.2 or lower, making it vulnerable to CVE-2023-5966.
  2. Verify extension deployment feature status
    Access the EspoCRM admin panel and navigate to the extension deployment section (typically under Administration > Extensions or a similar menu path). Determine if the extension upload/install functionality is enabled and accessible.
    Affected if The extension deployment feature is enabled and accessible to privileged users.
  3. Confirm privileged user access to extensions
    Check the user roles and permissions configuration in EspoCRM admin panel. Identify which users or roles have permission to install or upload extensions.
    Affected if Any user role other than the highest-privilege admin has permission to deploy extensions, expanding the attack surface.
  4. Inspect writable directories for unexpected PHP files
    Search the web root and subdirectories (particularly the 'data', 'upload', or extension upload directories) for unfamiliar .php files that may have been uploaded via the vulnerability. Use file system inspection commands or the admin panel file manager if available.
    Affected if Unexpected PHP files exist in writable directories, indicating possible exploitation.

Your environment is affected if EspoCRM version 7.5.2 or lower is installed with the extension deployment feature enabled and accessible to privileged users who can upload zip archives.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.5.2
Interim mitigation

Restrict extension deployment permissions to minimal necessary admin users, implement strict validation of zip file contents (whitelist allowed file types, prevent path traversal, block PHP file uploads), and consider disabling the extension deployment feature until official patch is applied.

Recommended fix Moderate confidence

Latest stable EspoCRM release (version 7.5.3 or later)

  1. 1. Backup your EspoCRM database and files before performing any upgrade.
  2. 2. Download the latest stable version of EspoCRM from the official repository (https://github.com/espocrm/espocrm).
  3. 3. Review the upgrade instructions in the official EspoCRM documentation at https://docs.espocrm.com/administration/upgrading/.
  4. 4. Alternatively, if using a hosted solution, contact your hosting provider for managed upgrade options.
  5. 5. After upgrade, verify the extension upload functionality works correctly in Administration > Extensions.
  6. 6. Test that the arbitrary file upload vulnerability is patched by ensuring only valid extension packages can be uploaded.
Caveat Check EspoCRM release notes for breaking changes between your current version and the target version; major version jumps may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Espocrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5966 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data