| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pulse CMS up to 1.18. It has been rated as problematic. Affected is an unknown function of the file delete.php. This manipulation of the argument f causes path traversal. This vulnerability is handled as CVE-2010-0989. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in Pulse CMS up to 1.18 (Content Management System). Affected by this vulnerability is an unknown function of the file delete.php. The manipulation of the argument f with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
Directory traversal vulnerability in delete.php in Pulse CMS before 1.2.3 allows remote authenticated users to delete arbitrary files via directory traversal sequences in the f parameter.
The weakness was released 03/24/2010 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2010-0989 since 03/18/2010. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation requires a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
By approaching the search of inurl:delete.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.16 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 38947†), OSVDB (63167†) and Secunia (SA39011†). Entry connected to this vulnerability is available at VDB-52380. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
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: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CMS 1.16
Timeline
03/18/2010 🔍03/24/2010 🔍
03/24/2010 🔍
03/24/2010 🔍
03/26/2010 🔍
03/19/2015 🔍
05/03/2026 🔍
Sources
Advisory: securityfocus.com⛔Status: Confirmed
CVE: CVE-2010-0989 (🔍)
GCVE (CVE): GCVE-0-2010-0989
GCVE (VulDB): GCVE-100-52381
SecurityFocus: 38947
Secunia: 39011 - Pulse CMS Multiple Vulnerabilities, Highly Critical
OSVDB: 63167 - Pulse CMS delete.php f Parameter Traversal Arbitrary File Deletion
See also: 🔍
Entry
Created: 03/19/2015 12:22Updated: 05/03/2026 12:44
Changes: 03/19/2015 12:22 (49), 08/28/2017 09:15 (10), 05/03/2026 12:44 (19)
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.