CVE-2025-7612
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 | mobile_shop | 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-7612 is a critical SQL injection vulnerability in the Mobile Shop 1.0 application, specifically in the /login.php file. The vulnerability occurs because the 'email' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of SQL queries, potentially giving attackers access to the database to retrieve, modify, or delete sensitive data. The attack can be performed remotely without authentication and has a publicly available exploit. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, leading to the exposure, modification, or deletion of sensitive data. It threatens the confidentiality, integrity, and availability of your system. Attackers can disrupt services, manipulate data, and potentially take full control of the affected system, causing significant security risks and business continuity issues. [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 /login.php endpoint for SQL injection via the 'email' parameter. One common method is to use SQL injection testing tools or manual commands such as curl or sqlmap. For example, using sqlmap: sqlmap -u "http://targetsite/login.php" --data="[email protected]" --risk=3 --level=5 --batch. Alternatively, you can try sending crafted requests with SQL injection payloads in the 'email' parameter using curl, e.g., curl -X POST -d "email=' OR '1'='1" http://targetsite/login.php and observe if the response indicates SQL errors or unauthorized access. Additionally, Google dorking with queries like inurl:login.php can help identify potentially vulnerable targets. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements (parameterized queries) to ensure user input is treated as data, not executable SQL code. 2) Apply strict input validation and filtering on the 'email' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative as no known mitigations are documented for this specific vulnerability. [3, 2]