CMS Made Simple 2.2.8 FrontEndUsers class.FrontEndUsersManipulate.php __FEU__ injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.5 | $0-$5k | 0.00 |
A vulnerability was found in CMS Made Simple 2.2.8 (Content Management System) and classified as critical. This issue affects an unknown part of the file class.FrontEndUsersManipulate.php of the component FrontEndUsers. The manipulation of the argument __FEU__
as part of a Cookie leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in CMS Made Simple 2.2.8. In the module FrontEndUsers (in the file class.FrontEndUsersManipulate.php or class.FrontEndUsersManipulator.php), it is possible to reach an unserialize call with an untrusted __FEU__ cookie, and achieve authenticated object injection.
The bug was discovered 03/06/2019. The weakness was disclosed 04/11/2019 (Website). It is possible to read the advisory at newsletter.cmsmadesimple.org. The identification of this vulnerability is CVE-2019-9056 since 02/23/2019. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 36 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:class.FrontEndUsersManipulate.php 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.
The entries VDB-243114, VDB-243206, VDB-243283 and VDB-243691 are pretty similar.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: InjectionCWE: CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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
02/23/2019 🔍03/06/2019 🔍
04/11/2019 🔍
04/12/2019 🔍
05/29/2020 🔍
Sources
Advisory: newsletter.cmsmadesimple.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-9056 (🔍)
See also: 🔍
Entry
Created: 04/12/2019 06:56Updated: 05/29/2020 11:01
Changes: 04/12/2019 06:56 (58), 05/29/2020 11:01 (2)
Complete: 🔍
Cache ID: 3:847:103
No comments yet. Languages: en.
Please log in to comment.