| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in SugarCRM up to 5.2e. The impacted element is an unknown function of the component File Upload. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2009-2146. In addition, an exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in SugarCRM up to 5.2e. This affects an unknown functionality of the component File Upload. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Unrestricted file upload vulnerability in the Compose Email feature in the Emails module in Sugar Community Edition (aka SugarCRM) before 5.2f allows remote authenticated users to execute arbitrary code by uploading a file with only an extension in its name, then accessing the file via a direct request to a modified filename under cache/modules/Emails/, as demonstrated using .php as the entire original name.
The weakness was presented 06/22/2009 by Francesco "aScii" Ongaro (Website). The advisory is shared at ush.it. This vulnerability is uniquely identified as CVE-2009-2146 since 06/22/2009. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 5.2e eliminates this vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (8949), SecurityFocus (BID 35361†) and Secunia (SA35445†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: SugarCRM 5.2e
Timeline
06/13/2009 🔍06/15/2009 🔍
06/22/2009 🔍
06/22/2009 🔍
06/22/2009 🔍
03/17/2015 🔍
08/28/2025 🔍
Sources
Advisory: ush.itResearcher: Francesco "aScii" Ongaro
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2009-2146 (🔍)
GCVE (CVE): GCVE-0-2009-2146
GCVE (VulDB): GCVE-100-48693
SecurityFocus: 35361 - SugarCRM Email Attachment Arbitrary File Upload Vulnerability
Secunia: 35445 - SugarCRM Emails Module File Upload Vulnerability, Moderately Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 23:38Updated: 08/28/2025 18:02
Changes: 03/17/2015 23:38 (50), 11/11/2018 09:37 (7), 08/28/2025 18:02 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.