CVE-2025-7512
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-7512 is a critical SQL injection vulnerability in the Modern Bag 1.0 application, specifically in the /contact-back.php file. The vulnerability occurs because the 'contact-name' parameter from user input is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access and manipulation. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute arbitrary SQL commands without authentication, leading to unauthorized access to sensitive data, modification or deletion of database contents, full system control, and potential service disruptions. [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 identifying the presence of the vulnerable file '/contact-back.php' and testing the 'contact-name' parameter for SQL injection. One suggested method is to use Google dorking with the query 'inurl:contact-back.php' to find potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to send crafted inputs to the 'contact-name' parameter and observe for SQL errors or unexpected behavior. Specific commands are not provided in the resources. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: using prepared statements to ensure user inputs are treated as data and not executable SQL code; implementing strict input validation and filtering on the 'contact-name' parameter; limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations; and conducting regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [2, 3]