GreenCMS 2.3.0603 index.php?m=admin&c=media&a=fileconnect content cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GreenCMS 2.3.0603. This affects an unknown function of the file index.php?m=admin&c=media&a=fileconnect. This manipulation of the argument content as part of Parameter causes cross-site request forgery. This vulnerability is handled as CVE-2018-11670. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability classified as critical was found in GreenCMS 2.3.0603. Affected by this vulnerability is some unknown processing of the file index.php?m=admin&c=media&a=fileconnect. The manipulation of the argument content as part of a Parameter 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 confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in GreenCMS v2.3.0603. There is a CSRF vulnerability that allows attackers to execute arbitrary PHP code via the content parameter to index.php?m=admin&c=media&a=fileconnect.
The bug was discovered 06/01/2018. The weakness was released 06/01/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-11670 since 06/01/2018. 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. Technical details and also a public exploit are known.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
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 Exploit-DB (44825). Entry connected to this vulnerability is available at VDB-118622. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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 request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
06/01/2018 🔍06/01/2018 🔍
06/01/2018 🔍
06/01/2018 🔍
06/02/2018 🔍
05/24/2025 🔍
Sources
Product: github.comAdvisory: 108
Status: Not defined
CVE: CVE-2018-11670 (🔍)
GCVE (CVE): GCVE-0-2018-11670
GCVE (VulDB): GCVE-100-118621
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 06/02/2018 20:06Updated: 05/24/2025 11:49
Changes: 06/02/2018 20:06 (58), 02/11/2020 19:24 (4), 03/19/2023 13:43 (4), 05/24/2025 11:49 (18)
Complete: 🔍
Cache ID: 216::103
Submit
Duplicate
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.