| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in YzmCMS 5.2 and classified as problematic. Impacted is an unknown function of the file admin/content/search.html. Performing a manipulation of the argument searinfo as part of Parameter results in cross site scripting. This vulnerability was named CVE-2018-19849. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in YzmCMS 5.2. It has been classified as problematic. This affects an unknown part of the file admin/content/search.html. The manipulation of the argument searinfo as part of a Parameter 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:
An issue was discovered in YzmCMS 5.2. XSS exists via the admin/content/search.html searinfo parameter.
The bug was discovered 11/08/2018. The weakness was presented 12/04/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-19849 since 12/04/2018. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 26 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:admin/content/search.html 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/yzmcms/yzmcms/
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
11/08/2018 🔍12/04/2018 🔍
12/04/2018 🔍
12/04/2018 🔍
12/05/2018 🔍
04/17/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2018-19849 (🔍)
GCVE (CVE): GCVE-0-2018-19849
GCVE (VulDB): GCVE-100-127473
Entry
Created: 12/05/2018 08:15Updated: 04/17/2020 11:44
Changes: 12/05/2018 08:15 (57), 04/17/2020 11:44 (1)
Complete: 🔍
Cache ID: 216:88A:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.