GreenCMS 2.3.0603 Log File index.php cross-site request forgery

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in GreenCMS 2.3.0603. It has been declared as problematic. This vulnerability affects some unknown processing of the file index.php?m=admin&c=data&a=clear of the component Log File Handler. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity, and availability. CVE summarizes:

An issue was discovered in GreenCMS v2.3.0603. There is a CSRF vulnerability that allows attackers to delete a log file via the index.php?m=admin&c=data&a=clear URI.

The bug was discovered 11/20/2018. The weakness was disclosed 11/20/2018 (Website). The advisory is available at This vulnerability was named CVE-2018-19376 since 11/20/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.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-148218, VDB-182996, VDB-193312 and VDB-193824 are pretty similar.




CPE 2.3info

CPE 2.2info


VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍


VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9

VulDB Base Score: 5.4
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


11/20/2018 🔍
11/20/2018 +0 days 🔍
11/20/2018 +0 days 🔍
11/20/2018 +0 days 🔍
11/21/2018 +1 days 🔍
06/11/2023 +1663 days 🔍


Advisory: 114
Status: Not defined

CVE: CVE-2018-19376 (🔍)
See also: 🔍


Created: 11/21/2018 12:26 PM
Updated: 06/11/2023 08:57 AM
Changes: 11/21/2018 12:26 PM (55), 04/14/2020 11:32 AM (1), 06/11/2023 08:57 AM (3)
Complete: 🔍
Cache ID: 3:A31:40


No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!