Pixelimity 1.0 admin/portfolio.php data[title] Persistent cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Pixelimity 1.0. This affects an unknown function of the file admin/portfolio.php. This manipulation of the argument data[title] as part of SVG Element causes cross site scripting (Persistent). This vulnerability appears as CVE-2018-19919. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Pixelimity 1.0. It has been declared as problematic. Affected by this vulnerability is an unknown code of the file admin/portfolio.php. The manipulation of the argument data[title] as part of a SVG Element leads to a cross site scripting vulnerability (Persistent). The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Pixelimity 1.0 has Persistent XSS via the admin/portfolio.php data[title] parameter, as demonstrated by a crafted onload attribute of an SVG element.
The bug was discovered 11/03/2018. The weakness was presented 12/06/2018 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2018-19919 since 12/06/2018. The attack can be launched remotely. A single 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.
The vulnerability was handled as a non-public zero-day exploit for at least 33 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/portfolio.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.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.6
VulDB Base Score: 2.4
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔍
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
Name: PersistentClass: Cross site scripting / Persistent
CWE: 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
11/03/2018 🔍12/06/2018 🔍
12/06/2018 🔍
12/06/2018 🔍
12/07/2018 🔍
06/13/2023 🔍
Sources
Product: github.comAdvisory: 19
Status: Not defined
CVE: CVE-2018-19919 (🔍)
GCVE (CVE): GCVE-0-2018-19919
GCVE (VulDB): GCVE-100-127663
Entry
Created: 12/07/2018 09:26Updated: 06/13/2023 14:30
Changes: 12/07/2018 09:26 (58), 04/18/2020 18:37 (1), 06/13/2023 14:30 (3)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.