itsourcecode Tailoring Management System 1.0 customeradd.php sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in itsourcecode Tailoring Management System 1.0. This affects an unknown function of the file customeradd.php. Performing a manipulation of the argument fullname/address/phonenumber/sex/email/city/comment results in sql injection. This vulnerability is known as CVE-2024-6372. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability, which was classified as critical, was found in itsourcecode Tailoring Management System 1.0. This affects an unknown code of the file customeradd.php. The manipulation of the argument fullname/address/phonenumber/sex/email/city/comment 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 advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-6372. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept. By approaching the search of inurl:customeradd.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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://itsourcecode.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 6.3
CNA 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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
06/27/2024 🔍06/27/2024 🔍
08/20/2024 🔍
Sources
Vendor: itsourcecode.comAdvisory: github.com
Status: Not defined
CVE: CVE-2024-6372 (🔍)
GCVE (CVE): GCVE-0-2024-6372
GCVE (VulDB): GCVE-100-269805
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/27/2024 07:23Updated: 08/20/2024 22:20
Changes: 06/27/2024 07:23 (55), 08/20/2024 22:20 (30)
Complete: 🔍
Submitter: galaxy
Cache ID: 216::103
Submit
Accepted
- Submit #364752: itsourcecode Tailoring Management System Project In PHP 1.0 SQL Injection (by galaxy)
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.