CVE-2025-9599
BaseFortify
Publication date: 2025-08-29
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-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-9599 is a critical SQL injection vulnerability in the itsourcecode Apartment Management System version 1.0, specifically in the /setting/month_setup.php file. The vulnerability occurs because the txtMonthName parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access and manipulation, such as modifying, deleting, or exposing sensitive data. The attack can be launched remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of records, and potential full control over the affected system. It can also disrupt services and compromise data integrity. Since the attack requires no authentication and can be performed remotely, it poses a significant security risk. [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 /setting/month_setup.php endpoint for SQL injection via the txtMonthName parameter. One approach is to use sqlmap, a popular automated SQL injection tool, with a command like: sqlmap -u "http://target/setting/month_setup.php" --data="txtMonthName=test" --risk=3 --level=5. Additionally, Google Dorking can help identify vulnerable targets using queries such as: inurl:setting/month_setup.php. A proof-of-concept exploit uses time-based blind SQL injection payloads (e.g., injecting SLEEP(5)) to confirm the vulnerability. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing or updating the affected component or product to a version without the vulnerability. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the txtMonthName parameter. 4) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [1, 2, 3]