CVE-2025-9598
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-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-9598 is a critical SQL injection vulnerability in the Apartment Management System 1.0, specifically in the file /setting/year_setup.php. It occurs because the input parameter txtXYear is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by extracting, altering, or deleting data. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database records, full system compromise, and disruption of service availability. Attackers can exploit it remotely without authentication, leading to significant risks to system security and business continuity. [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 /setting/year_setup.php endpoint for SQL injection on the txtXYear parameter. A practical method is to use the sqlmap tool with a command like: sqlmap -u "http://<target>/apartment/setting/year_setup.php" --data="MULTIPART txtXYear" --batch --dbs. Additionally, a time-based blind SQL injection payload such as "111' AND (SELECT 6470 FROM (SELECT(SLEEP(5)))ygGM) AND 'epFI'='epFI" can be used to confirm the vulnerability by observing delayed server responses. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection. 2) Applying strict input validation and filtering on the txtXYear parameter to ensure only expected input is accepted. 3) Minimizing database user privileges by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits of the code and system to detect and fix vulnerabilities promptly. [1]