Tramyardg hotel-mgmt-system 2022.4 /app/dao/CustomerDAO.php sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Tramyardg hotel-mgmt-system 2022.4 and classified as critical. Affected by this issue is some unknown functionality of the file /app/dao/CustomerDAO.php. The manipulation leads to sql injection. This vulnerability is handled as CVE-2022-48090. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in Tramyardg hotel-mgmt-system 2022.4 (Hospitality Software) and classified as critical. Affected by this vulnerability is an unknown functionality of the file /app/dao/CustomerDAO.php. The manipulation 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 summary by CVE is:
Tramyardg hotel-mgmt-system version 2022.4 is vulnerable to SQL Injection via /app/dao/CustomerDAO.php.
The weakness was disclosed 01/13/2023 as 21. The advisory is shared at github.com. This vulnerability is known as CVE-2022-48090 since 12/29/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:app/dao/CustomerDAO.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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: 🔍
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
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
12/29/2022 🔍01/13/2023 🔍
01/13/2023 🔍
04/07/2025 🔍
Sources
Advisory: 21Status: Not defined
CVE: CVE-2022-48090 (🔍)
GCVE (CVE): GCVE-0-2022-48090
GCVE (VulDB): GCVE-100-218317
Entry
Created: 01/13/2023 11:15 PMUpdated: 04/07/2025 11:17 PM
Changes: 01/13/2023 11:15 PM (40), 02/07/2023 09:16 AM (11), 04/07/2025 11:17 PM (16)
Complete: 🔍
Cache ID: 18:36A:40
No comments yet. Languages: en.
Please log in to comment.