SourceCodester Billing Management System 1.0 POST Parameter ajax_service.php drop_services sql injection
Summary
A vulnerability, which was classified as critical, has been found in SourceCodester Billing Management System 1.0. This issue affects some unknown processing of the file ajax_service.php of the component POST Parameter Handler. This manipulation of the argument drop_services causes sql injection. This vulnerability is tracked as CVE-2023-2595. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability has been found in SourceCodester Billing Management System 1.0 (Billing Software) and classified as critical. Affected by this vulnerability is an unknown functionality of the file ajax_service.php of the component POST Parameter Handler. The manipulation of the argument drop_services 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 disclosed 05/09/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-2595. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. By approaching the search of inurl:ajax_service.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
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.sourcecodester.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 (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
05/09/2023 🔍05/09/2023 🔍
05/09/2023 🔍
09/07/2024 🔍
Sources
Vendor: sourcecodester.comAdvisory: github.com
Status: Not defined
CVE: CVE-2023-2595 (🔍)
GCVE (CVE): GCVE-0-2023-2595
GCVE (VulDB): GCVE-100-228397
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/09/2023 14:19Updated: 09/07/2024 16:18
Changes: 05/09/2023 14:19 (43), 06/01/2023 08:06 (2), 06/01/2023 08:10 (28), 09/07/2024 16:18 (22)
Complete: 🔍
Submitter: yastar
Cache ID: 216::103
Submit
Accepted
- Submit #153776: Billing Management System v1.0 /smartbilling_source_code/ajax_service.php POST parameter 'drop_services' exists SQL injection vulnerability (by yastar)
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.