Yii Yii2 Gii up to 2.2.1 Generator.php messageCategory code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 1.11 |
Summary
A vulnerability marked as critical has been reported in Yii Yii2 Gii up to 2.2.1. Impacted is an unknown function of the file Generator.php. The manipulation of the argument messageCategory leads to code injection. This vulnerability is referenced as CVE-2020-36655. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Yii Yii2 Gii up to 2.2.1. This issue affects an unknown code of the file Generator.php. The manipulation of the argument messageCategory with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Yii Yii2 Gii before 2.2.2 allows remote attackers to execute arbitrary code via the Generator.php messageCategory field. The attacker can embed arbitrary PHP code into the model file.
The weakness was published 01/21/2023 as 433. The advisory is shared at github.com. The identification of this vulnerability is CVE-2020-36655 since 01/21/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
By approaching the search of inurl:Generator.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.2.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0322). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Yii2 Gii 2.2.2
Timeline
01/21/2023 🔍01/21/2023 🔍
01/21/2023 🔍
07/02/2025 🔍
Sources
Advisory: 433Status: Confirmed
CVE: CVE-2020-36655 (🔍)
GCVE (CVE): GCVE-0-2020-36655
GCVE (VulDB): GCVE-100-219125
EUVD: 🔍
Entry
Created: 01/21/2023 13:40Updated: 07/02/2025 15:49
Changes: 01/21/2023 13:40 (42), 02/18/2023 09:39 (11), 04/02/2025 23:16 (16), 07/02/2025 15:49 (1)
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.