oretnom23 Sanitization Management System 1.0 Master.php?f=delete_inquiry ID sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in oretnom23 Sanitization Management System 1.0. It has been classified as critical. This impacts an unknown function of the file /php-sms/classes/Master.php?f=delete_inquiry. Performing a manipulation of the argument ID results in sql injection. This vulnerability is reported as CVE-2022-43350. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in oretnom23 Sanitization Management System 1.0. This affects an unknown code block of the file /php-sms/classes/Master.php?f=delete_inquiry. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Sanitization Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /php-sms/classes/Master.php?f=delete_inquiry.
The weakness was disclosed 11/07/2022. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-43350 since 10/17/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: 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
10/17/2022 🔍11/07/2022 🔍
11/07/2022 🔍
12/05/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-43350 (🔍)
GCVE (CVE): GCVE-0-2022-43350
GCVE (VulDB): GCVE-100-213057
Entry
Created: 11/07/2022 21:57Updated: 12/05/2022 09:54
Changes: 11/07/2022 21:57 (39), 12/05/2022 09:54 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.