CVE-2025-7605
BaseFortify
Publication date: 2025-07-14
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anisha | avl_rooms | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7605 is a critical SQL injection vulnerability in version 1.0 of the AVL Rooms project, specifically in the /profile.php file. It occurs because the application uses the first_name parameter from user input directly in SQL queries without proper validation or sanitization. This allows attackers to inject malicious SQL code, leading to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely exploit the system without authentication, leading to unauthorized retrieval or modification of sensitive information, disruption of services, and potential full system compromise. It threatens the confidentiality, integrity, and availability of your system and data. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /profile.php endpoint for SQL injection via the first_name parameter. One method is to send crafted HTTP requests with SQL injection payloads in the first_name parameter and observe the response for SQL errors or unexpected behavior. Additionally, attackers may use Google dorking with queries like "inurl:profile.php" to identify vulnerable targets. Example command using curl to test injection: curl -X GET 'http://target/profile.php?first_name=admin' OR '1'='1'. Monitoring for unusual database errors or unexpected query results can also help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements to ensure user input is treated as data, not executable SQL code. 2) Implement strict input validation and filtering on the first_name parameter to enforce expected data formats. 3) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known countermeasures have been reported. [1, 2]