Victor CMS 1.0 POST Request posts.php?source=add_post post_title sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Victor CMS 1.0. This issue affects some unknown processing of the file admin/posts.php?source=add_post of the component POST Request Handler. Such manipulation of the argument post_title leads to sql injection. This vulnerability is referenced as CVE-2021-46458. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Victor CMS 1.0 (Content Management System) and classified as critical. Affected by this issue is an unknown part of the file admin/posts.php?source=add_post of the component POST Request Handler. The manipulation of the argument post_title with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability.
The weakness was published 01/31/2022. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2021-46458 since 01/24/2022. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 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
01/24/2022 🔍01/31/2022 🔍
01/31/2022 🔍
02/04/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2021-46458 (🔍)
GCVE (CVE): GCVE-0-2021-46458
GCVE (VulDB): GCVE-100-192020
Entry
Created: 01/31/2022 18:47Updated: 02/04/2022 07:31
Changes: 01/31/2022 18:47 (40), 02/04/2022 07:31 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.