CreatiWity wityCMS 0.6.2 Search for User Discovery /admin/user/users Nickname/email/firstname/lastname/groupe sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CreatiWity wityCMS 0.6.2. It has been declared as critical. Affected by this issue is some unknown functionality of the file /admin/user/users of the component Search for User Discovery. Executing a manipulation of the argument Nickname/email/firstname/lastname/groupe as part of Parameter can lead to sql injection. This vulnerability is handled as CVE-2018-16251. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability has been found in CreatiWity wityCMS 0.6.2 and classified as critical. This vulnerability affects some unknown processing of the file /admin/user/users of the component Search for User Discovery. The manipulation of the argument Nickname/email/firstname/lastname/groupe as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality. CVE summarizes:
A "search for user discovery" injection issue exists in Creatiwity wityCMS 0.6.2 via the "Utilisateur" menu. No input parameters are filtered, e.g., the /admin/user/users Nickname, email, firstname, lastname, and groupe parameters.
The weakness was released 06/20/2019. This vulnerability was named CVE-2018-16251 since 08/30/2018. The exploitation appears to be easy. The attack can be initiated remotely. Required for exploitation is a single authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entry connected to this vulnerability is available at VDB-136785. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/30/2018 🔍06/20/2019 🔍
06/20/2019 🔍
10/07/2023 🔍
Sources
Product: github.comAdvisory: 157
Status: Not defined
CVE: CVE-2018-16251 (🔍)
GCVE (CVE): GCVE-0-2018-16251
GCVE (VulDB): GCVE-100-136786
See also: 🔍
Entry
Created: 06/20/2019 22:08Updated: 10/07/2023 10:27
Changes: 06/20/2019 22:08 (39), 06/26/2020 12:50 (17), 10/07/2023 10:27 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.