payfort-php-SDK up to 2018-04-26 success.php fort_id cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in payfort-php-SDK up to 2018-04-26. The impacted element is an unknown function of the file success.php. Executing a manipulation of the argument fort_id as part of Parameter can lead to cross site scripting. This vulnerability is handled as CVE-2018-19188. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in payfort-php-SDK up to 2018-04-26 (Programming Language Software). It has been declared as problematic. This vulnerability affects an unknown function of the file success.php. The manipulation of the argument fort_id as part of a Parameter leads to a cross site scripting vulnerability. 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. CVE summarizes:
The Amazon PAYFORT payfort-php-SDK payment gateway SDK through 2018-04-26 has XSS via the success.php fort_id parameter.
The bug was discovered 11/13/2018. The weakness was released 11/14/2018 (Website). The advisory is available at securityfocus.com. This vulnerability was named CVE-2018-19188 since 11/11/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:success.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 SecurityFocus (BID 105930†). Entries connected to this vulnerability are available at VDB-126825, VDB-126827 and VDB-126828. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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
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
11/11/2018 🔍11/13/2018 🔍
11/14/2018 🔍
11/14/2018 🔍
11/14/2018 🔍
11/15/2018 🔍
06/06/2023 🔍
Sources
Advisory: 12⛔Status: Not defined
CVE: CVE-2018-19188 (🔍)
GCVE (CVE): GCVE-0-2018-19188
GCVE (VulDB): GCVE-100-126826
SecurityFocus: 105930 - Amazon PayFort payfort-php-SDK Multiple Cross Site Scripting Vulnerabilities
See also: 🔍
Entry
Created: 11/15/2018 08:05Updated: 06/06/2023 13:36
Changes: 11/15/2018 08:05 (61), 04/12/2020 18:59 (3), 06/06/2023 13:36 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.