| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pulse CMS 1.2.2. It has been classified as problematic. The impacted element is an unknown function of the file view.php. Performing a manipulation of the argument f results in cross site scripting. This vulnerability was named CVE-2010-1080. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Pulse CMS 1.2.2 (Content Management System). It has been classified as problematic. This affects an unknown code block of the file view.php. The manipulation of the argument f with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in view.php in Pulse CMS 1.2.2 allows remote attackers to inject arbitrary web script or HTML via the f parameter.
The weakness was presented 02/20/2010 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2010-1080 since 03/23/2010. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
By approaching the search of inurl:view.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (56430), SecurityFocus (BID 38356†), OSVDB (62475†) and Secunia (SA38650†). See VDB-52621 for similar entry. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/20/2010 🔍02/22/2010 🔍
02/22/2010 🔍
02/22/2010 🔍
03/23/2010 🔍
03/23/2010 🔍
03/19/2015 🔍
08/28/2017 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2010-1080 (🔍)
GCVE (CVE): GCVE-0-2010-1080
GCVE (VulDB): GCVE-100-52323
X-Force: 56430
SecurityFocus: 38356 - Pulse CMS 'view.php' Cross Site Scripting Vulnerability
Secunia: 38650 - Pulse CMS Cross-Site Scripting and Directory Traversal, Less Critical
OSVDB: 62475 - Pulse CMS view.php f Parameter XSS
See also: 🔍
Entry
Created: 03/19/2015 12:22Updated: 08/28/2017 09:16
Changes: 03/19/2015 12:22 (49), 08/28/2017 09:16 (12)
Complete: 🔍
Cache ID: 216:CD8:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.