CVE-2025-5705
BaseFortify
Publication date: 2025-06-06
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 |
|---|---|---|
| fabian | real_estate_property_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-5705 is a critical SQL injection vulnerability in version 1.0 of the Real Estate Property Management System, specifically in the /Admin/Property.php file. It occurs because the 'cmbCat' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, data leakage, modification, or deletion of data, and potentially full system compromise. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized database access, exposure of sensitive information, data modification or deletion, full system compromise, and potential service disruption. Since it can be exploited remotely without authentication, attackers can easily exploit it to damage the system or steal data, threatening the confidentiality, integrity, and availability of your system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'cmbCat' parameter in the /Admin/Property.php file for SQL injection. Proof-of-concept payloads include boolean-based blind and time-based blind SQL injection techniques, such as using MySQL's RLIKE operator or the SLEEP() function to observe responses or delays. Tools like sqlmap can be used to automate detection. Additionally, attackers may be identified by searching for the vulnerable URL pattern using Google dorking with queries like "inurl:Admin/Property.php" to find exposed instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. Enforce strict input validation and filtering on the 'cmbCat' parameter to ensure inputs conform to expected formats. Minimize database user permissions by avoiding high-privilege accounts such as root or admin for routine operations. Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known countermeasures have been reported. [2, 3, 1]