CVE-2025-5611
BaseFortify
Publication date: 2025-06-04
Last updated on: 2025-06-10
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-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-5611 is a critical SQL injection vulnerability in the CodeAstro Real Estate Management System version 1.0, specifically in the file /submitpropertyupdate.php. It occurs because the 'id' parameter is not properly sanitized, allowing an attacker to inject malicious SQL code remotely. This can lead to unauthorized access or manipulation of the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can remotely exploit the flaw to access or manipulate sensitive data in the database without authentication. This could lead to data breaches, unauthorized data modification, or disruption of service. [2]
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 file submitpropertyupdate.php and testing the 'id' parameter for SQL injection. One method is to use Google dorking with the query "inurl:submitpropertyupdate.php" to identify potentially vulnerable targets. For direct testing, you can use tools like curl or sqlmap to send crafted requests to the 'id' parameter and observe if SQL injection is possible. Example command with sqlmap: sqlmap -u "http://target/submitpropertyupdate.php?id=1" --batch. Alternatively, manual testing with curl: curl "http://target/submitpropertyupdate.php?id=1' OR '1'='1" and checking for SQL error messages or unexpected responses. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
There are no known countermeasures or mitigations currently available for this vulnerability. The suggested immediate step is to replace the affected product (CodeAstro Real Estate Management System version 1.0) with an alternative solution. Additionally, restricting access to the vulnerable endpoint and monitoring for exploitation attempts may help reduce risk until a fix or patch is available. [2]