dbcve.org
Sugar SalesApplication · Sugarcrm

CVE-2004-1228

MEDIUM · 6.4 CVSS v2.0 Published 2005-01-10
Fix available
A fix is available. Upgrade to after 2.0.1c or later.
See remediation →
73/100
Remediation priority · Elevated
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
The install scripts in SugarCRM Sugar Sales 2.0.1c and earlier are not removed after installation, which allows attackers to obtain the MySQL administrative password in cleartext from an installation form, or to cause a denial of service by changing database settings to the default.

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 SugarCRM Sugar Sales 2.0.1c and earlier, the installation scripts are not automatically removed after the installation process completes. This leaves the installation pages accessible on the web server, allowing attackers to access the installation form which exposes the MySQL administrative password in cleartext. Additionally, attackers can re-run the installer to modify database settings to defaults, causing denial of service.

MitigationRemove all installation scripts (install.php and related files) from the web root immediately after completing the installation, or configure web server access controls to block external access to the installation directory.

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
Sugar SalesApplication
Affected:<= 2.0.1c

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:N/A:P

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. Locate install.php in web root
    Search the web document root directory for the file 'install.php' - common paths include /var/www/html/, /home/user/public_html/, or the SugarCRM installation directory itself
    Affected if install.php file exists in or under the web document root
  2. Find installation directory contents
    Look for an 'install' subdirectory or related installation files such as install.js, install.css, or install.php under the SugarCRM application directory
    Affected if installation directory or related files (install.php, install.js, install.css) are present in the web-accessible area
  3. Test web accessibility of installation scripts
    Attempt to access http://[your-server]/install.php or the corresponding URL for your SugarCRM installation using a web browser or curl command
    Affected if the installation page loads and is accessible over HTTP/HTTPS
  4. Check installation status file
    Examine the SugarCRM configuration file (typically config.php or config_override.php in the application root) for presence of database configuration strings or installation completion markers
    Affected if the application appears fully installed (database configured) yet install.php remains accessible
  5. Verify installation was not cleaned up
    Review the web server filesystem to confirm whether install.php and associated files were intentionally removed or remain as leftover files after initial installation
    Affected if install.php and installation files remain in place after the CRM is operational

If install.php and related installation files exist in a web-accessible location on a SugarCRM installation that has already been configured with database credentials, the system is vulnerable to CVE-2004-1228.

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 2.0.1c
Interim mitigation

Remove all installation scripts (install.php and related files) from the web root immediately after completing the installation, or configure web server access controls to block external access to the installation directory.

Fix this in Sugar Sales Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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