Image Sharing Script 4.13 /categorypage.php token Reflected cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Image Sharing Script 4.13. It has been classified as problematic. This vulnerability affects unknown code of the file /categorypage.php. Performing a manipulation of the argument token with the input "><img src=i onerror=prompt(1)> results in cross site scripting (Reflected).
The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability classified as problematic has been found in Image Sharing Script 4.13. This affects an unknown code block of the file /categorypage.php. The manipulation of the argument token with the input value "><img src=i onerror=prompt(1)> leads to a cross site scripting vulnerability (Reflected). CWE is classifying the issue as CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. This is going to have an impact on integrity.
The weakness was presented 01/16/2017 by Hasan Emre Ozer as EDB-ID 41080 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
A public exploit has been developed by Hasan Emre Ozer and been published immediately after the advisory. The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:categorypage.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 vulnerability database at Exploit-DB (41080). See VDB-95366, VDB-95371, VDB-95372 and VDB-95374 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.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: 🔍
Exploiting
Name: ReflectedClass: Cross site scripting / Reflected
CWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Hasan Emre Ozer
Download: 🔍
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
01/16/2017 🔍01/16/2017 🔍
01/16/2017 🔍
01/17/2017 🔍
07/23/2020 🔍
Sources
Advisory: EDB-ID 41080Researcher: Hasan Emre Ozer
Status: Not defined
GCVE (VulDB): GCVE-100-95373
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 01/17/2017 11:11Updated: 07/23/2020 10:54
Changes: 01/17/2017 11:11 (48), 07/23/2020 10:54 (2)
Complete: 🔍
Cache ID: 216:247: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.