CVE-2025-7757
BaseFortify
Publication date: 2025-07-17
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 |
|---|---|---|
| phpgurukul | land_record_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-7757 is a critical SQL injection vulnerability in the PHPGurukul Land Record System version 1.0, specifically in the /edit-property.php file. The vulnerability occurs because the 'editid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can modify or delete data, retrieve sensitive information, and compromise the confidentiality, integrity, and availability of the system. Since no authentication is required, the risk of attack is high and can severely impact system security and business continuity. [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 /edit-property.php endpoint for SQL injection via the 'editid' parameter. A proof-of-concept involves sending a crafted GET request to /landrecordsys/admin/edit-property.php with the 'editid' parameter set to a payload that induces a delay (e.g., using SQL sleep function) to confirm injection. Tools like sqlmap can be used to automate detection. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:edit-property.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'editid' parameter, minimizing database user privileges by avoiding use of high-privilege accounts for routine operations, and conducting regular security audits. If possible, replacing the affected component with an alternative product is suggested. [2, 3, 1]