CVE-2025-14900
BaseFortify
Publication date: 2025-12-19
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 |
|---|---|---|
| codeastro | real_estate_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?
This vulnerability is a SQL injection flaw in the CodeAstro Real Estate Management System version 1.0, specifically in the administrator endpoint file /admin/userdelete.php. It occurs because the system improperly handles the 'ID' parameter, allowing an attacker to manipulate this input to inject malicious SQL code. This manipulation can alter the SQL queries executed by the application, potentially leading to unauthorized access or modification of the database. The vulnerability requires some level of authentication but can be exploited remotely. [2, 3]
How can this vulnerability impact me? :
The vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker exploiting this SQL injection flaw can gain unauthorized access to sensitive data, modify or delete data, and potentially disrupt system operations. Since the vulnerability affects the administrator endpoint, it could allow attackers with some level of access to escalate their privileges or cause significant damage to the database and application functionality. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable endpoint /admin/userdelete.php in the CodeAstro Real Estate Management System version 1.0. Attackers may use Google Dorking with queries such as 'inurl:admin/userdelete.php' to identify vulnerable targets. To detect exploitation attempts on your system, you can monitor web server logs for suspicious requests containing SQL injection patterns in the 'id' parameter. For example, you can use commands like: 1. Using grep to find suspicious requests in Apache logs: grep 'admin/userdelete.php' /var/log/apache2/access.log | grep 'id=' 2. Using a network monitoring tool like tcpdump to capture HTTP requests to the endpoint: tcpdump -A -s 0 'tcp port 80 and (((ip dst host your_server_ip) and (tcp dst port 80)))' | grep 'userdelete.php' 3. Using SQL injection detection tools or scanners against the endpoint to verify vulnerability. Note that exploitation requires authenticated access with elevated privileges, so monitoring admin panel access logs is also recommended. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /admin/userdelete.php endpoint to only trusted and authenticated administrators, as exploitation requires elevated privileges. Since no patches or countermeasures are currently documented, it is recommended to replace or update the affected component or product if possible. Additionally, implement input validation and parameterized queries to prevent SQL injection. Monitoring and logging access to the admin panel and the vulnerable endpoint can help detect and respond to exploitation attempts. Applying web application firewalls (WAF) rules to block malicious SQL injection payloads targeting the 'id' parameter can also reduce risk. [3, 2]