CVE-2025-7178
BaseFortify
Publication date: 2025-07-08
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 |
|---|---|---|
| fabian | food_distributor_site | 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-7178 is a critical SQL injection vulnerability in the code-projects Food Distributor Site 1.0, specifically in the /admin/login.php file. It occurs because the 'Username' parameter is not properly sanitized, allowing attackers to inject malicious SQL code. This flaw lets attackers manipulate the backend database by injecting SQL commands remotely without authentication, potentially compromising the system's confidentiality, integrity, and availability. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute unauthorized SQL commands on the database through the login interface. They can add, delete, modify, or view sensitive data, leading to data breaches, loss of data integrity, and potential disruption of service. Since the exploit is publicly available and easy to execute without authentication, it poses a high risk to affected systems. [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 /admin/login.php endpoint for SQL injection on the Username parameter. One approach is to use SQL injection testing tools or manual injection attempts with payloads such as ' OR '1'='1 or ' OR 'a'='a to observe if the application behaves unexpectedly or returns database errors. Additionally, Google dorking with queries like "inurl:admin/login.php" can help identify potentially vulnerable instances. Specific commands could include using curl or sqlmap, for example: sqlmap -u "http://target/admin/login.php" --data "Username=admin&Password=pass" -p Username --batch. Monitoring network traffic for suspicious SQL injection patterns or unexpected database errors in logs can also aid detection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component with an alternative product, as no known countermeasures or patches are documented. Restricting access to the /admin/login.php page via network controls or web application firewall (WAF) rules to block malicious input patterns targeting the Username parameter can help reduce risk. Additionally, monitoring for exploitation attempts and applying input validation or parameterized queries if possible are recommended interim measures until a secure fix or replacement is implemented. [1]