| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Grav CMS up to 1.2.x. Impacted is an unknown function. This manipulation causes cross site scripting (Reflected). This vulnerability is tracked as CVE-2018-5233. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Grav CMS up to 1.2.x (Content Management System). It has been declared as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a cross site scripting vulnerability (Reflected). 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:
Cross-site scripting (XSS) vulnerability in system/src/Grav/Common/Twig/Twig.php in Grav CMS before 1.3.0 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to admin/tools.
The bug was discovered 01/07/2017. The weakness was disclosed 03/16/2018 as [CVE-2018-5233] Grav CMS admin plugin Reflected Cross Site Scripting (XSS) vulnerability as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. This vulnerability is known as CVE-2018-5233 since 01/05/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly 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 178 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.3.0 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Researcher Base Score: 7.4
Researcher Vector: 🔍
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
Name: ReflectedClass: Cross site scripting / Reflected
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CMS 1.3.0
Timeline
01/07/2017 🔍07/04/2017 🔍
01/05/2018 🔍
03/16/2018 🔍
03/19/2018 🔍
03/19/2018 🔍
01/14/2020 🔍
Sources
Advisory: [CVE-2018-5233] Grav CMS admin plugin Reflected Cross Site Scripting (XSS) vulnerabilityStatus: Not defined
CVE: CVE-2018-5233 (🔍)
GCVE (CVE): GCVE-0-2018-5233
GCVE (VulDB): GCVE-100-114757
Entry
Created: 03/19/2018 08:00Updated: 01/14/2020 17:16
Changes: 03/19/2018 08:00 (70), 01/14/2020 17:16 (2)
Complete: 🔍
Cache ID: 216::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.