CVE-2025-7514
BaseFortify
Publication date: 2025-07-13
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 |
|---|---|---|
| code-projects | modern_bag | 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-7514 is a critical SQL injection vulnerability in the Modern Bag 1.0 software, specifically in the /admin/contact-list.php file. It occurs because the 'idStatus' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database by retrieving, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. Attackers can remotely execute arbitrary SQL commands without authentication, threatening the confidentiality, integrity, and availability of the affected system. [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 vulnerable parameter 'idStatus' in the URL /admin/contact-list.php for SQL injection. A common method is to use tools like sqlmap to automate detection. For example, running sqlmap against the URL with the parameter idStatus can confirm the vulnerability, e.g., `sqlmap -u "http://127.0.0.1/ModernBag_Web_PHP-master/admin/contact-list.php?idStatus=8" --batch`. Additionally, a time-based blind SQL injection test can be performed by appending payloads such as `idStatus=8 AND (SELECT 4160 FROM (SELECT(SLEEP(5)))UfEi)` to observe delays indicating injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'idStatus' parameter to ensure it conforms to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected component with a secure alternative. [2, 3]