CVE-2025-6479
BaseFortify
Publication date: 2025-06-22
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 |
|---|---|---|
| carmelo | simple_pizza_ordering_system | 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-6479 is a critical SQL injection vulnerability in the Simple Pizza Ordering System version 1.0, specifically in the /salesreport.php file. The vulnerability occurs because the 'dayfrom' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially leading to unauthorized access to the database, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute arbitrary SQL commands on the affected system without authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, and potentially full system compromise or service disruption. The impact includes loss of data confidentiality, integrity, and availability. [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 'dayfrom' parameter in the /salesreport.php file for SQL injection. Tools like sqlmap can be used to automate detection. For example, you can run a command such as: sqlmap -u "http://target/salesreport.php" --data="dayfrom=1" --risk=3 --level=5 --batch to test for SQL injection. Additionally, boolean-based blind and time-based blind SQL injection techniques can be used manually by injecting payloads that use MySQL functions like EXTRACTVALUE or SLEEP to observe responses and delays. Also, Google dorking with the query "inurl:salesreport.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'dayfrom' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. If possible, replace or update the affected component to a version without this vulnerability. [2, 3, 1]