dbcve.org
EspocrmApplication

CVE-2021-3539

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-04
Fix available
A fix is available. Upgrade to after 6.1.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
EspoCRM 6.1.6 and prior suffers from a persistent (type II) cross-site scripting (XSS) vulnerability in processing user-supplied avatar images. This issue was fixed in version 6.1.7 of the product.

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 · moderate confidence

EspoCRM versions 6.1.6 and prior contain a persistent (type II) cross-site scripting vulnerability in the avatar image upload and processing functionality. User-supplied avatar images are not properly sanitized, allowing malicious scripts to be stored in the system and executed when other users view the affected avatar.

MitigationUpgrade EspoCRM to version 6.1.7 or later to remediate this vulnerability. Until then, restrict avatar upload permissions to trusted users and monitor for suspicious content.

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:<= 6.1.6

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed version
    Locate the EspoCRM version information in your installation, typically found in the admin panel under 'About' or in a version.php file within the application directory
    Affected if The installed version is 6.1.6 or any earlier version
  2. Confirm avatar upload functionality is accessible
    Verify that users in your environment have the ability to upload or change their profile avatar image, typically found in user profile settings
    Affected if Avatar upload feature is enabled and accessible to users
  3. Check for untrusted user access
    Review which users have permission to upload avatars - this includes regular user accounts, contacts, or any entity type that supports avatar attachments
    Affected if Users without full trust can upload content to the system
  4. Compare version against affected range
    If version cannot be directly determined, cross-reference your installation metadata or admin panel with the affected version range
    Affected if Your installed version is 6.1.6 or lower

You are affected if your EspoCRM installation is version 6.1.6 or earlier and users have access to the avatar upload feature.

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.

From vendor data
Upgrade available Upgrade to a release after 6.1.6
Interim mitigation

Upgrade EspoCRM to version 6.1.7 or later to remediate this vulnerability. Until then, restrict avatar upload permissions to trusted users and monitor for suspicious content.

Fix this in Espocrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3539 — 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-2021-3539 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