CVE-2004-1227
Overview
CVE-2004-1227 is a known-severity vulnerability affecting sugarcrm sugar_sales. It was published on January 10, 2005.
Technical Description
Directory traversal vulnerability in SugarCRM Sugar Sales 2.0.1c and earlier allows remote attackers to read arbitrary files and possibly execute arbitrary PHP code via .. (dot dot) sequences in the (1) module, (2) action, or (3) theme parameters to index.php, (4) the theme parameter to Login.php, and possibly other parameters or scripts.
Remediation
Check the references section for vendor advisories and patches from sugarcrm. Update sugar_sales to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| sugarcrm | sugar_sales | 0 | Affected |
References
Frequently Asked Questions
What is CVE-2004-1227?
CVE-2004-1227 is a known-severity vulnerability affecting sugarcrm sugar_sales. It was published on January 10, 2005.
How severe is CVE-2004-1227?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2004-1227?
Check the references section for vendor advisories and patches from sugarcrm. Update sugar_sales to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2004-1227?
CyberStrike's AI-powered security agents can automatically detect CVE-2004-1227 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.