CVE-2025-7611
BaseFortify
Publication date: 2025-07-14
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 |
|---|---|---|
| anisha | wedding_reservation | 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
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, modification or deletion of data, full system control, and potential service disruption. Attackers can remotely execute malicious SQL queries without authentication, compromising data integrity and confidentiality. [1, 2]
Can you explain this vulnerability to me?
This vulnerability is a critical SQL injection flaw in the Wedding Reservation 1.0 application, specifically in the /global.php file. It occurs because the application does not properly validate or sanitize the 'lu' parameter, allowing attackers to inject malicious SQL code remotely. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data. [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 'lu' parameter in the /global.php file for SQL injection. One common method is to use time-based blind SQL injection techniques, such as injecting a payload that causes a delay using the MySQL SLEEP() function. For example, you can use curl or a browser to send a request like: http://target/global.php?lu=1' OR SLEEP(5)--+ and observe if the response is delayed, indicating vulnerability. Automated tools like sqlmap can also be used to test the parameter for SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering on the 'lu' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. [2]