CVE-2008-2045 json
Absolute path traversal vulnerability in SugarCRM Sugar Community Edition 4.5.1 and 5.0.0 allows remote attackers to read arbitrary files v…
published 2008-05-01 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-2042
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.2%
- EPSS 5.2% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
Absolute path traversal vulnerability in SugarCRM Sugar Community Edition 4.5.1 and 5.0.0 allows remote attackers to read arbitrary files via a full path in the URL parameter to modules/Feeds/Feed.php, which places the contents into a related cache file in the .cache/feeds directory.
Patch / fix
Timeline
- First public exploit (EDB-5521)
- Published
Exploit prediction
5.21% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5521 SugarCRM Community Edition 4.5.1/5.0.0 - File Disclosure webapps, 2008-04-29
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
sugarcrm.com
/forums/showthread.php?t=31688
patch
-
securityfocus.com
/bid/28981
vdb-entry, patch
-
sugarcrm.com
/forums/showthread.php?t=32252
patch
-
secunia.com
/advisories/30002
third-party-advisory, patch, vendor-advisory
-
exploit-db.com
/exploits/5521
exploit
-
securityfocus.com
/archive/1/491417/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2008/1388/references
vdb-entry
- sugarcrm.com /docs/Release_Notes/CommunityEdition_ReleaseNotes_5.0d/Sugar_Release_Notes_5.0d.2.6.html
-
securityreason.com
/securityalert/3844
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42087
vdb-entry
- security-assessment.com /files/advisories/2008-04-29_SugarCRM_local_file_disclosure.pdf
Sources
- CVE List CVE-2008-2045
- NVD CVE-2008-2045
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.