responsive-coming-soon-page Plugin 1.1.18 on WordPress wp-admin/admin.php counter_title_icon cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in responsive-coming-soon-page Plugin 1.1.18 on WordPress and classified as problematic. This affects an unknown part of the file wp-admin/admin.php. Executing a manipulation of the argument counter_title_icon as part of Parameter can lead to cross site scripting. This vulnerability is registered as CVE-2018-5657. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in responsive-coming-soon-page Plugin 1.1.18 on WordPress (WordPress Plugin). It has been declared as problematic. This vulnerability affects an unknown code of the file wp-admin/admin.php. The manipulation of the argument counter_title_icon 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:
An issue was discovered in the responsive-coming-soon-page plugin 1.1.18 for WordPress. XSS exists via the wp-admin/admin.php counter_title_icon parameter.
The bug was discovered 01/12/2018. The weakness was published 01/13/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-5657 since 01/12/2018. The attack can be initiated remotely. A single authentication is needed for 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.
By approaching the search of inurl:wp-admin/admin.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.
Similar entries are available at VDB-111851, VDB-111852, VDB-111853 and VDB-111854. 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: 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
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
01/12/2018 🔍01/12/2018 🔍
01/12/2018 🔍
01/13/2018 🔍
01/13/2018 🔍
12/23/2019 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-5657 (🔍)
GCVE (CVE): GCVE-0-2018-5657
GCVE (VulDB): GCVE-100-111850
See also: 🔍
Entry
Created: 01/13/2018 12:28Updated: 12/23/2019 09:58
Changes: 01/13/2018 12:28 (59), 12/23/2019 09:58 (1)
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.