Kashipara Billing Software 1.0 HTTP POST Request party_submit.php party_name sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Kashipara Billing Software 1.0. This impacts an unknown function of the file party_submit.php of the component HTTP POST Request Handler. Executing a manipulation of the argument party_name can lead to sql injection. This vulnerability is registered as CVE-2024-0495. It is possible to launch the attack remotely. Furthermore, an exploit is available.
Details
A vulnerability has been found in Kashipara Billing Software 1.0 (Billing Software) and classified as critical. This vulnerability affects an unknown function of the file party_submit.php of the component HTTP POST Request Handler. The manipulation of the argument party_name with an unknown input 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, integrity, and availability.
The weakness was published 01/12/2024. The advisory is shared for download at github.com. This vulnerability was named CVE-2024-0495. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. By approaching the search of inurl:party_submit.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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
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 (VulDB): 🔍
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: 🔍
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
01/12/2024 🔍01/12/2024 🔍
01/12/2024 🔍
02/02/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-0495 (🔍)
GCVE (CVE): GCVE-0-2024-0495
GCVE (VulDB): GCVE-100-250600
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/12/2024 01:26 PMUpdated: 02/02/2024 02:50 PM
Changes: 01/12/2024 01:26 PM (43), 02/02/2024 02:46 PM (2), 02/02/2024 02:50 PM (28)
Complete: 🔍
Submitter: heishou
Cache ID: 244:A24:40
Submit
Accepted
- Submit #266147: www.kashipara.com BILLING SOFTWARE 1.0 SQL injection vulnerability (by heishou)
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.