CVE-2025-9471
BaseFortify
Publication date: 2025-08-26
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 |
|---|---|---|
| admerc | apartment_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
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, and potential full compromise of the system. Attackers can exploit this remotely without authentication, which may disrupt services and compromise business continuity. [1]
Can you explain this vulnerability to me?
CVE-2025-9471 is a critical SQL injection vulnerability in version 1.0 of the Apartment Management System, specifically in the file /maintenance/add_maintenance_cost.php. The vulnerability occurs because the 'id' parameter from user input is directly used in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data modification or deletion, and even full system compromise or service disruption. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter `id` in the `/maintenance/add_maintenance_cost.php` endpoint for SQL injection. You can use tools like sqlmap to automate detection. Example commands include: - Using sqlmap: sqlmap -u "http://target/maintenance/add_maintenance_cost.php?id=22" --batch - Manual testing with payloads: - Boolean-based blind SQL injection test: id=22' RLIKE (SELECT (CASE WHEN (2564=2564) THEN 22 ELSE 0x28 END))-- - Time-based blind SQL injection test: id=22' AND (SELECT SLEEP(5))-- These payloads can be appended to the URL parameter to observe behavior changes indicating SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to prevent SQL injection. - Apply strict input validation and filtering on the `id` parameter to ensure it matches expected formats. - Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts like `root` or `admin` for application database access. - Conduct a security audit of the affected code and system to identify and fix similar vulnerabilities. These steps help prevent exploitation and reduce the risk of unauthorized data access or manipulation. [1]