CVE-2025-5710
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-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-5710 is a critical SQL injection vulnerability in the Real Estate Property Management System version 1.0, specifically in the /Admin/InsertState.php file. It occurs because the input parameter 'txtStateName' is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized access, data leakage, modification, or deletion in the database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, modification or deletion of database records, full system compromise, and potential service disruption. Since it can be exploited remotely without authentication, attackers can manipulate the database leading to loss of data integrity, confidentiality, and availability. [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 /Admin/InsertState.php endpoint for SQL injection in the txtStateName parameter. A proof-of-concept payload for a time-based blind SQL injection is: txtStateName=111' AND (SELECT 2022 FROM (SELECT(SLEEP(5)))RoLv) AND 'cqWw'='cqWw&button=Submit, which causes a delay in the response if vulnerable. Tools like sqlmap can be used to automate detection. Additionally, searching for the vulnerable URL using Google dorking (e.g., inurl:Admin/InsertState.php) can help identify targets. Example command using sqlmap: sqlmap -u "http://target/Admin/InsertState.php" --data="txtStateName=111&button=Submit" --time-sec=5 --technique=T --batch [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the txtStateName parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known countermeasures are currently available. [2, 3]