dbcve.org
SugarcrmApplication

CVE-2020-7472

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-12
Fix available
A fix is available. Upgrade to 8.0.7 / 9.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 authorization bypass and PHP local-file-include vulnerability in the installation component of SugarCRM before 8.0, 8.0 before 8.0.7, 9.0 before 9.0.4, and 10.0 before 10.0.0 allows for unauthenticated remote code execution against a configured SugarCRM instance via crafted HTTP requests. (This is exploitable even after installation is completed.).

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

Authorization bypass combined with PHP local-file-include vulnerability in SugarCRM's installation component allows unauthenticated attackers to achieve remote code execution via crafted HTTP requests. The critical flaw persists even after installation completes, indicating the installation routes remain exposed or vulnerable.

MitigationUpgrade SugarCRM to version 8.0.7, 9.0.4, 10.0.0 or later. Consider restricting access to installation paths at the web server level as an additional layer of defense.

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
SugarcrmApplication
Affected:>= 8.0.0, < 8.0.7>= 9.0.0, < 9.0.4

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed SugarCRM version
    Locate the version file in the SugarCRM installation directory or access the About/Version information in the application admin panel. Common locations include a version.php file or the system settings area.
    Affected if The installed version falls within 8.0.0 to 8.0.6 OR 9.0.0 to 9.0.3 (prior to the fixed releases 8.0.7 and 9.0.4).
  2. Verify installation directory accessibility
    Attempt to access the /install or /installation directory path via HTTP/HTTPS from the web server root. Check if the installation wizard or setup pages are reachable without authentication.
    Affected if The installation routes remain publicly accessible after the initial setup has completed.
  3. Inspect installation directory for remaining files
    Review the web server filesystem for the presence of installation-related PHP files (such as install.php, setup.php, or related modules) in publicly accessible web directories.
    Affected if Installation PHP files remain in the web-accessible directory structure and are not removed or restricted after installation.
  4. Check web server configuration for installation path rules
    Review the web server configuration (Apache .htaccess, Nginx config, or equivalent) to determine if access controls or rewrite rules are in place to block or restrict access to installation paths.
    Affected if No access restrictions are configured for installation paths, leaving them exposed to unauthenticated requests.

A defender is affected if the installed SugarCRM version is 8.0.0-8.0.6 or 9.0.0-9.0.3 AND the installation directory or its files remain accessible without authentication.

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 8.0.7 / 9.0.4 or later
Fixed in 8.0.79.0.4
Interim mitigation

Upgrade SugarCRM to version 8.0.7, 9.0.4, 10.0.0 or later. Consider restricting access to installation paths at the web server level as an additional layer of defense.

Recommended fix High confidence

SugarCRM 8.0.7 or later; SugarCRM 9.0.4 or later

  1. Backup your SugarCRM database and file system before proceeding with any upgrade
  2. Download SugarCRM version 8.0.7 or later for 8.x installations, or version 9.0.4 or later for 9.x installations from the official SugarCRM support portal
  3. Follow SugarCRM's standard upgrade documentation for your specific version path
  4. Ensure the upgrade completes successfully and verify all modules function correctly after the upgrade
  5. Test that the installation component vulnerability is no longer exploitable by verifying the fix is applied
Caveat Review SugarCRM release notes for your specific upgrade path as minor version upgrades may include configuration or workflow changes

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

Fix this in Sugarcrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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